Related
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)
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.
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
The following probably sounds like a dumb question, but I'm genuinely confused. Would I be able to flash the SGH-1337 version of Lineage OS onto my SGH-1337M model of the Samsung S4? Or are they completely different models? Any answers will be greatly appreciated.
TipTopHiatus said:
The following probably sounds like a dumb question, but I'm genuinely confused. Would I be able to flash the SGH-1337 version of Lineage OS onto my SGH-1337M model of the Samsung S4? Or are they completely different models? Any answers will be greatly appreciated.
Click to expand...
Click to collapse
Maybe you will find an answer there: https://forum.xda-developers.com/ga...anadian-s4-i337m-jfltecan-rom-t3101107/page39
kurtn said:
Maybe you will find an answer there: https://forum.xda-developers.com/ga...anadian-s4-i337m-jfltecan-rom-t3101107/page39
Click to expand...
Click to collapse
Thanks. I'll check those out. Now that I view Lineage OS, they only have nightly builds available for the S4, which is not what I am looking for.
TipTopHiatus said:
Thanks. I'll check those out. Now that I view Lineage OS, they only have nightly builds available for the S4, which is not what I am looking for.
Click to expand...
Click to collapse
Nightly lineageOS build is the most stable thing you will find, besides stock ROM. Most other custom ROMs are based on lineageOS.
kurtn said:
Nightly lineageOS build is the most stable thing you will find, besides stock ROM. Most other custom ROMs are based on lineageOS.
Click to expand...
Click to collapse
But aren't nightly builds being updated nightly because they're still buggy and in the development phase? Also, I couldn't find anything better, so I've settled with GoldenEye 5.0.1. It works super well, and it runs smoothly. It also doesn't make the upper screen feel like the bottom of a clothing iron lol.
TipTopHiatus said:
But aren't nightly builds being updated nightly because they're still buggy and in the development phase?..........
Click to expand...
Click to collapse
Just an FYI...
What you had asked is the reminisce from the former CyanogenMod build structure.
CyanogenMod used to use the label "Nightly" for builds that may/might be unstable. Like a prerelease of its "Stable" builds.
Not long after the Official Launch of LineageOS, they had streamlined and such that had added "Stability" to the builds and changed the term "Nightly" to mean Stable Builds that are automated to be released with the fixes and such that were approved and pushed via Gitlab.
So LineageOS doesn't use the term "Stable" any longer since the "Nightly" builds are considered Stable Builds that are released on a Daily Basis (for the most part).
This is not to, personally, mean that Nightly Builds are without its bugs and such that they strive to improve on.
I've used Nightly Builds and had various degrees of issues I've reported but, most of the time, the Nightly Builds has been pretty stable for me.
Sorry for the lengthy explanation but, I do hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
Just an FYI...
What you had asked is the reminisce from the former CyanogenMod build structure.
CyanogenMod used to use the label "Nightly" for builds that may/might be unstable. Like a prerelease of its "Stable" builds.
Not long after the Official Launch of LineageOS, they had streamlined and such that had added "Stability" to the builds and changed the term "Nightly" to mean Stable Builds that are automated to be released with the fixes and such that were approved and pushed via Gitlab.
So LineageOS doesn't use the term "Stable" any longer since the "Nightly" builds are considered Stable Builds that are released on a Daily Basis (for the most part).
This is not to, personally, mean that Nightly Builds are without its bugs and such that they strive to improve on.
I've used Nightly Builds and had various degrees of issues I've reported but, most of the time, the Nightly Builds has been pretty stable for me.
Sorry for the lengthy explanation but, I do hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks for the information. Have a good one!