Related
[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<
tabletUI for ANY DEVICE running AOSP, CM10.1, or CM10.2
{
"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"
}
Check out post 2 for way more screenshots!
All you need is to get the latest version of the Auto-Patcher.(or ApG)
Linux/Mac: Check out mateorod's thread for instructions on getting the auto-patcher set up and how to use it.
Windows: Check Kobik77's post on ApG and download the latest version of ApG, which puts everything you need to make these patches together for you automatically!
Once you have that all set up just run your favourite AOSP, CM or SlimBean rom through the auto-patcher, patching for tabletUI. Auto-patcher will automatically detect your rom type and use the appropriate patches. It really could not be any easier!
(In ApG if you must set the rom type then use AOSP for Slim)
Make A Backup Before Trying Any Of These Mods! I will not be responsible for your data loss.
The Auto-Patcher will produce an update.zip and a restore.zip. I recommend moving both to your device before flashing.
Flash the produced update.zip in recovery and reboot.
Enjoy the tabletUI goodness!
If you do experience any issues, or your device bootloops, or you just want to go back to the way things were before applying the tabletUI mod, boot into recovery and flash the restore.zip. This will replace ALL of the original rom files and you should be able to boot up normally.
Confirmed Devices (Roms):
Nexus 7 - 2013 (AOSP/CM)
Nexus 10 (AOSP/CM)
Nexus 7 (CM)
Galaxy Tab 2 (AOSP/CM/SLIM)
Asus Transformer TF101 (CM)
Nook Color (CM)
Motorola Xoom (CM) - Thanks LQQKS!
Acer Iconia A500 (CM) - Thanks rsriram22!
Galaxy Grand Duos GT-I9082 (CM) - Thanks @karipari95! (who says setting dpi to 160 perfects the tablet look!)
If you have just patched a new device, not on this list let me know so I can add it!Known Issues:
This mod is going away from what android has been moving toward for a few months so there are a few issues with some android features. I personally think that the gains outweigh the losses in this, but depending on your device usage YMMV.
Multi-User: If you use multiple users on your device then this mod is probably not going to work well for you. In tests it seems that any user will get the notifications for all users. They can't be clicked but they do come through and can be seen.
Encryption: I have had a report that enabling Security/Encrypt tablet in conjunction with tabletUI mod will lead to a boot loop.
Notifications: Most notifications will work fine, however certain ones will not be seen:
Storage related notifications may not be seen. For instance the popup to enable mass storage when you plug into your computer.
Persistent Alarm Notification will not be seen when you have the alarm set.
Preferences: Sometimes certain options in Settings (having to do with appearance) will either no longer be present, or will have no effect when changed.
Launcher/Apps: On devices with smaller screens and lower resolutions the default launcher may not look very good after applying tabletUI mods. I recommend using a custom launcher from the play store, like Nova/Holo, which let you customize appearances. Also some apps may appear a little odd, or be missing content. This only affects small, low-res screens and is minimal.(see Youtube: missing/squished "Like"/"Subscribe" buttons)
Bugs/Requests:
If you have to report a failed attempt at patching a rom please include as much detail as you can, including the log from auto-patcher (full log please, not copy/paste of terminal output) and the rom and device you are trying to patch for (link to thread/source appreciated)
Please do not report failures for roms other than those stated as working in this thread; currently AOSP, CM10.1, and SlimBean.
Please do not post requests for support for roms which are not currently supported.
Be aware that some roms which are called "AOSP/AOSP based" are actually heavily modified by their developer already and these patches may fail in that case.
If you need to report an issue with some function that worked on your device before flashing the tabletUI mod but isn't working after, a log of the failure can be very helpful in coming to a solution, and is appreciated. Please check the Known Issues above before reporting.
Thanks/Credits
mateorod & pastime1971 for the amazingly versatile Auto-Patcher!
kobik77 for ApG which really makes the Auto-Patcher accessible for everyone!
barrmulio for all his work on tabletUI!
All the happy, willing testers: brGabriel, 138, 19cam92, dlumberg, astro_75, rraaka, tuxafgmur, and anyone else I am forgetting! Without you...:crying:!
All the awesome, talented developers on XDA that bring us these great roms for our devices! Thanks to each and every one of you for helping make this community what it is!
All my fellow tabletUI fans out there, who don't want to accept an awkward user interface!
Anyone else who has slipped my mind at the moment, and anyone who has ever contributed anything to XDA you're great too!:highfive:
Screenshots:
Galaxy Tab 2 7.0: CM10.1 (for more see here)
Galaxy Tab 2 7.0: SlimBean
Galaxy Tab 2 10.1: CM10.1 (for more see here)
Nexus 10: CM10.1
Nexus 10: AOSP
Asus Transformer TF101: CM10.1
one more just in case
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
i9apps said:
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
Click to expand...
Click to collapse
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.
"Recent Apps" style?
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
SGH-i200 said:
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
Click to expand...
Click to collapse
Thank you for the report. I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?
@SGH-i200
I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!
Awesome work Caldair!
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Didgesteve said:
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Click to expand...
Click to collapse
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.
Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.
Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:
These changes help reduce the extra load that tabletUI seems to put on the gpu!
Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)
And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
LQQKS said:
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
Click to expand...
Click to collapse
From the look of your log I think there is something wrong with your ApG installation.
I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. But the patcher really should be working for that rom.
Maybe you could try completely removing ApG and starting fresh, that may help. I hope!
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
LQQKS said:
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
Click to expand...
Click to collapse
Glad to hear it!
And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!
Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!
ATTACHMENTS REMOVED.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
drewski_1 said:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Click to expand...
Click to collapse
Gatak said:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
Click to expand...
Click to collapse
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.
For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.
Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.
Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.
These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.
Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.
WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy
Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.
arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it
oops, i haven't noticed esmazter's phrase
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.
Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
oliman99 said:
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
Click to expand...
Click to collapse
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
rjmxtech said:
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
Click to expand...
Click to collapse
I have been considering switching from cm 12.1 to slim lp on my fire. When you say additional customization what does that elude to? Theming and visual, or performance customization?
blueberry.sky said:
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
Click to expand...
Click to collapse
I've got xposed on the cm 12.1 rom. Haven't tried yet on SlimLP though.
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
blueberry.sky said:
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
Click to expand...
Click to collapse
I successfully flashed v2.1 of SlimLP, and then I tried v75 and v78 of wanams xposed (preceded with the mandatory installation apk). Both versions led to bootloop; I was able to remove the bootloop by using the uninstallation apk.
Since I want/needed xprivacy I switched to CM12.1 but gapps has stopped working. When there's a new version of SlimLP I might try again.
EDIT: I fixed the gapps in CM12.1 (12/04 built) by (1) doing a factory reset and (2) uninstalling the Playpermissionfix module in xposed. In retrospect I probably could skip (1) and do (2) only. Play store is still slightly wonky but it mostly works, and youtube definitely works 100%.
Damn, it's really a pain that SlimLP doesn't support xposed. I want xprivacy as well.
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
misticalx said:
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
Click to expand...
Click to collapse
The decision to decide for yourself is always in your hands. It is their rom to develop it how they want. If you do not like it, don't use it (as you have indiciated), but don't throw blame on a dev for not including support for something.
Edit: As far as I can tell this is no longer needed on the latest Lineage OS 14.1 builds.
I edited another module I found here to do what I needed it to do. Basically, Android Wear won't run on CM14.1 Nightlies because they are UserDebug so I made a script to get around this issue. I think that as long as Magisk is enabled that it should persist with each update instead of having to manually edit the build.props yourself each time. I take no credit for the script except my small edits.
The original script is for enabling Google Assistant and can be found here.
This has no warranty in the very unlikely event bad things happen I'm not responsible. I made this for myself and just thought it would be useful to others.
Special Thanks to stangri and Setialpha for their hard work on their modules that I used to make this.
Awesome, but why not just edit build.prop? Why are the nightlies set to userdebug in the first place?
I'm pretty sure they've always been like that. The reason why you would use this is it's a hassle to manually edit it every day when you update to the new nightly.
Jisifus said:
Awesome, but why not just edit build.prop? Why are the nightlies set to userdebug in the first place?
Click to expand...
Click to collapse
The whole point of magisk is to NOT modify the actual build.prop or make ANY changes in /system
How do you enable magisk?
Sent from my A0001 using XDA-Developers mobile app
This is how Android wear works on cm 14.1
https://youtu.be/NasiUcEnkoo
ashokmor007 said:
This is how Android wear works on cm 14.1
https://youtu.be/NasiUcEnkoo
Click to expand...
Click to collapse
My script basically does the same thing except you don't have to manually edit the file they time you update your os because it always makes sure it's the correct property. So using magisk and my script is a much better solution.