Related
{
"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.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
[ROM][UNOFFICIAL][4.4.4][WEEKLIES] SlimKat [m4], ROM for the HTC One Mini
Contributors
pandasa123
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2014-08-13
Last Updated 2014-08-12
Downloads
ROM - Full ROMs every week
SlimGapps - Download Google App package and other addons. Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Slim 7.0 Stable
Start of project
For full list: Click here
Click to expand...
Click to collapse
List all Questions and Off-Topic discussions in Q/A Thread
Remember, flash at own will! Don't message me and threaten me with a lawsuit because I may or may not have broken your device!
Issues
Waiting for this to fill
Thanks to:
SlimROMs for ROM
CyanogenMod for kernel
Click to expand...
Click to collapse
Installation Instructions
You must unlock your bootloader or be S-OFF.
You must have a custom recovery installed that allows SELinux.
Download the HTC One Mini build .
Locate Slim 4.4 Gapps here.
Fully wipe your device from Recovery if you are not coming from SlimKat already.
Reboot into recovery and install.
Hi bud. Just to confirm Rom boots fine and installs flawlessly! So far not noticed any issues. Unfortunately I'm a loyal candyRom user so will be bouncing back to that but good work and thanks for bringing this to the m4..cheers
Good luck on getting it official
Anyone found any bugs? I want to get rid of them for you guys by next build
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
dipje said:
I think people (including) me don't dare to install any non-sense ROM because of the overheating-and-phone-killing-issues that are apparently in the CM11 base on the mini (and every fork of it). Now, the error isn't in CM11, but I take from it that there are still reliability issues in getting a non-sense rom working to a point where it doesn't brick phones.
The issue is that on some phones CM11 runs fine for 5 months but then kills the phone, with others it's within two weeks.
And I don't blame anyone for some bricks that might have happened, but it does put me off from any non-sense (AOSP?) based rom, including this one. Are my fears justified?
Click to expand...
Click to collapse
Well that's up to the user if he wants a none sense ROM. I seen all the fuss about the issues etc even seen the Sense Fanboys loving that people are being scared off AOSP too. Tbh I don't see any problems with it my Rom been tested for awhile and is build from slim not CM with no issues at all... if people don't wanna try aosp then that's their loss....
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
dipje said:
Doesn't have to do with 'fanboys' or not, does it? I had some version of AOSP on most of my devices (also MIUI and such) and would like to try it on my M4, but seeing reports of dying phones on multiple AOSP versions make (even) me hesitant. Since it only happens on our device it's not in the AOSP base or CM11 base but in the device specific portion, like kernel, firmware binaries in the ROM and maybe configuration on some background daemons (thermald?)... was hoping you could take my doubt away .
Click to expand...
Click to collapse
Well I don't own this device anymore but the guy who tests builds doesn't have any issues with my ROM. This isn't my thread and I didn't build this ROM so you would have to take it up with the thread owner...
"On multiple aosp version" ???
Had no problems with any aosp rom on this device and I haven't ran sense for about a year now. No issues with pac,or slim and definitely none with candy which is my daily rom. Tbh I did have one issue with cm in the early days which I managed to recover from... But I put that down to my error... Flashing different kernels, installing performance mods/scripts etc and using different xposed modules.
Apologies for hijacking thread
Don't worry about the thread hijack lol...i wasn't paying attention..
I'm back from the hospital and i'm ready to build. t6vzw is brunching right now, and once it's done t6spr will start. after that, the m4 will get going and then my evita...so m4 users, expect your build to be ready by the end of tonight or so
slim m4 should be coming out today or tomorrow...the new server had a lot of build errors so i just fixed it for the evita
going to build for t6vzw, then t6spr, and then m4...
NEW BUILD! 7.6! Wait for around 15 min after this post is done and you'll see it. Check on the slim website for changelog...
http://downloads.codefi.re/ethanj99/pandasa123/Slim
Ok everyone, i'm building right now and this is the last time (i hope) that i move hosts
be a bit patient with me and i'll try and get it uploaded as soon as I finish homework
http://downloads.codefi.re/pandasa123
EDIT: UPDATED! Enjoy
New build guys - 7.9 Weekly (FINALLY )
Changelog:
Settings: Slimrecents card/text color
Add ADB over network tile
frameworks/av updates aosp caf
frameworks/base updates aosp caf
audio-caf updates
updated apns
frameworks/native-caf updates
more translations
Click to expand...
Click to collapse
enjoy
pandasa123 said:
New build guys - 7.9 Weekly (FINALLY )
enjoy
Click to expand...
Click to collapse
Sorry, but I can't find 7.9, only 7.8.
Thanks for building slim for m4!
Hey guys, Slim 8.0 Stable is out! Enjoy
pandasa123 said:
Hey guys, Slim 8.0 Stable is out! Enjoy
Click to expand...
Click to collapse
Ok. but where to download ?
http://downloads.codefi.re/pandasa123/Slim
No root after installing this ROM. Kernel installed is TWRP. No other kernel seems to work
XOSP for Marshmallow is not developed and maintained anymore. No new builds can or will be done. Be sure to check XOSP Nougat out!
Siphonay’s ROM building project presents
UNOFFICIAL Xperia Open Source Project
{
"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"
}
Description
Xperia Open Source Project (XOSP) is a ROM based on CyanogenMod that aims to provide the user the look and feel of the Sony Xperia phones, with the flexibility and customization options of custom ROMs. It removes CyanogenMod apps but keeps some of its features, as its theme engine or its weather service. It comes with a package named XOSPApps providing the very multimedia and home apps coming with Xperia phones.
Status
This ROM's developement for Marshmallow has been stopped by the developers to focus on the Nougat version of the ROM. Some sources for Marshmallow aren't available anymore. Thus, new builds can't be done until CM14 for the HTC One M7 is released.
Bugs
This bug section has a specific protocol.
To each bug will be assignated one flag of the following:
C : CyanogenMod specific. This means the bug originates from the CyanogenMod sources and that it will be fixed by the CM developers in a future build.
F : Flavor specific. This means the bug originates from the ROM's flavor sources and that it will be fixed by its developers in a future build.
B : Build specific. This means the bug originates from the builds I do. Hopefully, this is very unlikely to happen.
U : Unknown. Not enough info (yet) to identify the origin of the bug.
Then, there will be if necessary some more textual info about the context of the bug, workaround in bold if available to avoid the bug before a fix. Every fixed bug will get struck.
C : Random reboots
This is a known issue in CM-based ROMs. It has been fixed in more recent CM sources, but since the XOSP-MM isn't buildable anymore, it can't be fixed on this ROM.
C : Flashlight quicksettings doesn't work properly
This is a known issue in CM-based ROMs. It has been fixed in more recent CM sources, but since the XOSP-MM isn't buildable anymore, it can't be fixed on this ROM. You can use an alternative flashlight app.
X : Viper4AndroidFX force-closes after switching to drawer view.
FIXED as of XOSP Release 6 Revision 3 (removed drawer view option). NOT FIXED if you updated from a version prior to XOSP 6.2. If you switch to drawer view, V4A won't launch again. To fix this, go into the Applications menu in the settings and delete the data for V4A.
X : One or more of the XOSPApps force-closes
This is a recurring bug in new releases of XOSP. It is easily fixed by updating the problematic apps with the Play Store.
X : Email app force-closes after clicking on "manual settings" when adding an Exchange ActiveSync account from the Accounts menu in the Settings.
I tested this on multiple devices using XOSP and experience the same issue. As a workaround, I suggest you use another e-mail client app with Exchange support. Thanks @Brakelseboer for the report of this bug. Here is the logcat.
B : Double tap to wake switch in XOSP settings does nothing and resets itself to disabled state
This is the normal behavior of this switch when the ROM is compiled without a kernel with double tap to wake support, which is the case of my XOSP build. I prefer not to do so because listening to digitizer inputs while the screen is off causes important battery drain.
You can, and are encouraged to report any bug you encounter with this ROM. Will be taken into account reports containing the following :
The build you are using
Clear steps to reproduce the bug
Optional logcat of when the bug happens
If possible, tell me if you experience the same bug on other CM-based ROMs
If possible, tell me if you experience the same bug on another device with the same ROM
Of course, any other information you judge useful
When meeting this criterias and if other users approve your report, it will be added to the list. Bugs encountered with the use of Xposed or a custom kernel will be discarded.
Downloads
FINAL MM UNOFFICIAL XOSP 6.3 for m7 BUILT 07-27-2016 md5 sum : 178570477a18591c67c9a52d10d98e61
Previous builds
UNOFFICIAL XOSP 6.3 for m7 BUILT 07-11-2016 md5 sum : cf8a26ceccba1d42369aa822c2d921b9
UNOFFICIAL XOSP 6.2 for m7 BUILT 07-08-2016 md5 sum : 4ad102d873c6f6946d3c70f9ae352f51
The XOSPApps for XOSP 6.3 package is mandatory to have the full XOSP experience. (click here for XOSPApps for builds prior to XOSP 6.3)
The OpenGapps package is recommended.
Frequently Asked Questions
When is the next build coming?
I can't give precise information about the next build. I try to do a new build each time there is a significant change in the ROM's sources (bugfixes, new features...), but keep in mind that I can only do this on my personal computer for now, and that I also do it on my free time. So please be patient!
Will you fix this bug?
Unfortunately, I'm not the person in charge of fixing the ROM's flaws internally. We have to wait until the bug is fixed in the upstream sources (either CyanogenMod, or the ROM developers of the one in this thread), and that I do a new build.
Will a Nougat version of this ROM be available?
I hope so! Again, this depends CyanogenMod 14 ever comes to our device, and if the ROM developers carry on to this version too. I can't say for sure, but if it is possible, it will be done.
About the HTC One M7 ROM Building Project by Siphonay
As an effort to keep our device alive, I'm trying to build the various existing CM flavors not already officially or unofficially available for it to keep its ecosystem varied, and provide its user a wide range of choice for their device.
If you like this ROM, you should definitely check out the other builds of this project!
Unofficial Xperia Open Source Project (XOSP) - Unofficial Android Open Kang Project (AOKP) - Unofficial PAC-ROM - OctOS M Community Build - UNOFFICIAL Tipsy OS 4.9 - OctOS M Community Build - Android Open Source Project + Substratum OMS (AOSP-OMS)
If you'd like to donate to the project (p.e. to fund a server to automate the builds in the future), I'd ask you first to consider if you have anything else more useful for you that you'd want to do with your money. If you really want to help this way, you can send me money with PayPal.
Sources
Kernel source
Device tree
Device manifest
XOSP source
Credits
CyanogenMod
XOSP
@nilac for his help
@malybru for the banner
nightwalkerkg for the logo
This is the first time I'm porting and building a ROM for another device Please leave your feedback on the ROM!
Great job ?
Sent from my powerful Intel inside using Tapatalk
I'll flash your rom asap good
Great to see this. Is this "camera fixed"? Most cm 13 Roms seem to be fixed now including Facebook and messenger app. I would love to flash this and provide feedback ASAP. Thanks for the contribution.
Sent from my HTC One using Tapatalk
kwattro76 said:
Great to see this. Is this "camera fixed"? Most cm 13 Roms seem to be fixed now including Facebook and messenger app. I would love to flash this and provide feedback ASAP. Thanks for the contribution.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I did not check Facebook, but the caméra indeed works flawlessly.
flash light and gps work ?
Siphoné said:
I did not check Facebook, but the caméra indeed works flawlessly.
Click to expand...
Click to collapse
Facebook/Messenger works!
kwattro76 said:
Facebook/Messenger works!
Click to expand...
Click to collapse
Nice to hear !
The flashlight tile is bugged the same way as in other CM ROMs, unfortunately. GPS is working.
GPS didn't work actually. Pull up an address to navigate to and you'll see.
Sent from my HTC One using Tapatalk
Will the backlight module is one screen?
kwattro76 said:
GPS didn't work actually. Pull up an address to navigate to and you'll see.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It works for me, I used it last evening :/ I don't know what's the problem. Do you have a specific carrier model or is it the generic m7 ?
duffi200000 said:
Will the backlight module is one screen?
Click to expand...
Click to collapse
Sorry, I did not understand this question.
kwattro76 said:
GPS didn't work actually. Pull up an address to navigate to and you'll see.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yeah GPS does not work but the rest is great. The best android 6 rom atm for one m7! Very up to speed... But I need gps for sports!
ontwerp said:
Yeah GPS does not work but the rest is great. The best android 6 rom atm for one m7! Very up to speed... But I need gps for sports!
Click to expand...
Click to collapse
Thanks
Does other CM-based ROMs have the GPS not working ?
what about me ? I changed the display module and after I lock the screen does not turn on the light again until you reboot after reboot works,Put back and lock again illuminates larger screen
Great rom, best 6.0 i've used so far.
The gps is working on my device
is this rom have internet-pass through option...
duffi200000 said:
what about me ? I changed the display module and after I lock the screen does not turn on the light again until you reboot after reboot works,Put back and lock again illuminates larger screen
Click to expand...
Click to collapse
Do you experience this problem with other CM 13 ROMs ?
If this only happens to you, then it is an isolated bug and I can't do much about it, sorry :/
nandhul30 said:
is this rom have internet-pass through option...
Click to expand...
Click to collapse
If by internet pass-through you mean reverse USB tethering, then, no, unfortunately. However I do believe there are third party solutions to achieve this.
I tested the GPS once again and encountered no problem.
Please, anyone for whom GPS doesn't work, specify :
-How it doesn't work (is it imprecise? or is there no location at all?)
-If you use a variant of the m7, and which one
-If you experience the same problems with GPS with other CM13-based ROMs
Exchange Activesync FC when selecting manual input on serversettings
Siphonay’s ROM building project presents
UNOFFICIAL Android Open Kang Project
{
"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"
}
Description
Android Open Kang Project is a CyanogenMod-based ROM aiming to provide its users a stock Android experience with plenty of additional customization options. It also includes CyanogenMod apps and features, such as its theme engine.
Status
This ROM is active and can be built with the latest CyanogenMod sources available.
Bugs
This bug section has a specific protocol.
To each bug will be assignated one flag of the following:
C : CyanogenMod specific. This means the bug originates from the CyanogenMod sources and that it will be fixed by the CM developers in a future build.
F : Flavor specific. This means the bug originates from the ROM's flavor sources and that it will be fixed by its developers in a future build.
B : Build specific. This means the bug originates from the builds I do. Hopefully, this is very unlikely to happen.
U : Unknown. Not enough info (yet) to identify the origin of the bug.
Then, there will be if necessary some more textual info about the context of the bug, workaround in bold if available to avoid the bug before a fix. Every fixed bug will get struck.
No bugs to report at this time
You can, and are encouraged to report any bug you encounter with this ROM. Will be taken into account reports containing the following :
The build you are using
Clear steps to reproduce the bug
Optional logcat of when the bug happens
If possible, tell me if you experience the same bug on other CM-based ROMs
If possible, tell me if you experience the same bug on another device with the same ROM
Of course, any other information you judge useful
When meeting this criterias and if other users approve your report, it will be added to the list. Bugs encountered with the use of Xposed or a custom kernel will be discarded.
Downloads
UNOFFICIAL AOKP 6.0 Built 13-10-2016 md5 sum: 12e5abda48f6d8559ce635a592197f93
New in this build : Rebased on android-6.0.1_r72. Now build with the Linaro toolchain.
Previous builds
UNOFFICIAL AOKP 6.0 Built 09-26-2016 md5 sum: f6f433fca7f80c68e1398455fd204bc6
The OpenGapps package is recommended.
Frequently Asked Questions
When is the next build coming?
I can't give precise information about the next build. I try to do a new build each time there is a significant change in the ROM's sources (bugfixes, new features...), but keep in mind that I can only do this on my personal computer for now, and that I also do it on my free time. So please be patient!
Will you fix this bug?
Unfortunately, I'm not the person in charge of fixing the ROM's flaws internally. We have to wait until the bug is fixed in the upstream sources (either CyanogenMod, or the ROM developers of the one in this thread), and that I do a new build.
Will a Nougat version of this ROM be available?
I hope so! Again, this depends CyanogenMod 14 ever comes to our device, and if the ROM developers carry on to this version too. I can't say for sure, but if it is possible, it will be done.
About the HTC One M7 ROM Building Project by Siphonay
As an effort to keep our device alive, I'm trying to build the various existing CM flavors not already officially or unofficially available for it to keep its ecosystem varied, and provide its user a wide range of choice for their device.
If you like this ROM, you should definitely check out the other builds of this project!
Unofficial Xperia Open Source Project (XOSP) - Unofficial Android Open Kang Project (AOKP) - Unofficial PAC-ROM - OctOS M Community Build - UNOFFICIAL Tipsy OS 4.9 - OctOS M Community Build - Android Open Source Project + Substratum OMS (AOSP-OMS)
If you'd like to donate to the project (p.e. to fund a server to automate the builds in the future), I'd ask you first to consider if you have anything else more useful for you that you'd want to do with your money. If you really want to help this way, you can send me money with PayPal.
Sources
Kernel source
Device tree
Device manifest
AOKP source
Credits
CyanogenMod
AOKP
Of cource this ROM is Cam-fixed and Torch-fixed
OMG everything 's good but the theme engine so hard to use the weather always gone after apply a theme
Can I use SuperSU on this ROM? If yes, how do I install it?
Aqilz said:
Can I use SuperSU on this ROM? If yes, how do I install it?
Click to expand...
Click to collapse
Download the latest SuperSU zip here and flash it in the recovery like a gapps package.
This works for any ROM that doesn't include SuperSU by default!
how can we have fm radio and Camera 60fps like sense camera ?
haykweb said:
how can we have fm radio and Camera 60fps like sense camera ?
Click to expand...
Click to collapse
You can use the camera at 60fps with the stock application. In Video mode, go into the settings and set "Slow Motion" to "Slow Motion 60FPS", and "Video Quality" to either CIF or QVGA.
You can find the HTC FM Radio app on APK Mirror, but I can't guarantee you it will be working.
Siphoné said:
You can use the camera at 60fps with the stock application. In Video mode, go into the settings and set "Slow Motion" to "Slow Motion 60FPS", and "Video Quality" to either CIF or QVGA.
You can find the HTC FM Radio app on APK Mirror, but I can't guarantee you it will be working.
Click to expand...
Click to collapse
Sense stock camera have recording video quality HD 720 (60fps) ,why it not included in this customs for better camera,because aosp or cm camera is very bad.
haykweb said:
Sense stock camera have recording video quality HD 720 (60fps) ,why it not included in this customs for better camera,because aosp or cm camera is very bad.
Click to expand...
Click to collapse
Actually, the Old HTC Camera application is capable of recording 60fps 720p videos. You can get it here : http://www.apkmirror.com/apk/htc-corporation/camera-htc-corporation/
How does this ROM act in daily use? No random reboots? Microphone works?
Thanks for the port anyway!
It should work without major issues.
I would like to ask if there is any option to choose for have a vibration when the call is connected?
heij20032003 said:
I would like to ask if there is any option to choose for have a vibration when the call is connected?
Click to expand...
Click to collapse
Yes, vibration patterns is one of AOKP's features.
Siphoné said:
Yes, vibration patterns is one of AOKP's features.
Click to expand...
Click to collapse
so how can i make the setting? i cannot find it on my phone.
I think it is under the "ROM Settings" you can find in the Settings app.
there is no such option.....
so i download another app to solve the issue...
see if the function can be included in the later build
It was present on AOKP when it was based on previous Android version, so I assumed it would be on Marshmallow.
As always I'll do a new build if the developers ever add the feature, or any other one.
A new build has been released. AOKP has been rebased on r72. I also built the ROM with Linaro, so the performance should be a bit better.
Just installed this Rom everything is working so far except for notifications (no visuals only sound) and i cant open quicksettings
Edit: nevermind, reinstalling Rom+gapps fixed it
Does this ROM work for the Sprint variant?
Siphonay’s ROM building project presents
OctOS M Community Build
{
"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"
}
Description
OctOS is a ROM based on CyanogenMod aiming to provide the widest possible range of customization, providing all the CM features, additional customization options and several features from OmniROM.
Status
This ROM is in active developement. Its developing team still considers it as a work in progress.
Bugs
This bug section has a specific protocol.
To each bug will be assignated one flag of the following:
C : CyanogenMod specific. This means the bug originates from the CyanogenMod sources and that it will be fixed by the CM developers in a future build.
F : Flavor specific. This means the bug originates from the ROM's flavor sources and that it will be fixed by its developers in a future build.
B : Build specific. This means the bug originates from the builds I do. Hopefully, this is very unlikely to happen.
U : Unknown. Not enough info (yet) to identify the origin of the bug.
Then, there will be if necessary some more textual info about the context of the bug, workaround in bold if available to avoid the bug before a fix. Every fixed bug will get struck.
No bugs to report at this time
You can, and are encouraged to report any bug you encounter with this ROM. Will be taken into account reports containing the following :
The build you are using
Clear steps to reproduce the bug
Optional logcat of when the bug happens
If possible, tell me if you experience the same bug on other CM-based ROMs
If possible, tell me if you experience the same bug on another device with the same ROM
Of course, any other information you judge useful
When meeting this criterias and if other users approve your report, it will be added to the list. Bugs encountered with the use of Xposed or a custom kernel will be discarded.
Downloads
OctOS M Community Build Built 17-10-2016 md5 sum: d6d1e15cb6f0bbadd919d61b9321f171
The OpenGapps package is recommended.
Frequently Asked Questions
When is the next build coming?
I can't give precise information about the next build. I try to do a new build each time there is a significant change in the ROM's sources (bugfixes, new features...), but keep in mind that I can only do this on my personal computer for now, and that I also do it on my free time. So please be patient!
Will you fix this bug?
Unfortunately, I'm not the person in charge of fixing the ROM's flaws internally. We have to wait until the bug is fixed in the upstream sources (either CyanogenMod, or the ROM developers of the one in this thread), and that I do a new build.
Will a Nougat version of this ROM be available?
I hope so! Again, this depends CyanogenMod 14 ever comes to our device, and if the ROM developers carry on to this version too. I can't say for sure, but if it is possible, it will be done.
About the HTC One M7 ROM Building Project by Siphonay
As an effort to keep our device alive, I'm trying to build the various existing CM flavors not already officially or unofficially available for it to keep its ecosystem varied, and provide its user a wide range of choice for their device.
If you like this ROM, you should definitely check out the other builds of this project!
Unofficial Xperia Open Source Project (XOSP) - Unofficial Android Open Kang Project (AOKP) - Unofficial PAC-ROM - OctOS M Community Build - UNOFFICIAL Tipsy OS 4.9 - OctOS M Community Build - Android Open Source Project + Substratum OMS (AOSP-OMS)
If you'd like to donate to the project (p.e. to fund a server to automate the builds in the future), I'd ask you first to consider if you have anything else more useful for you that you'd want to do with your money. If you really want to help this way, you can send me money with PayPal.
Sources
Kernel source
Device tree
Device manifest
OctOS
Credits
CyanogenMod
OctOS
Link no found
antonio82 said:
Link no found
Click to expand...
Click to collapse
Fixed now, sorry about that!
Does this work for the Sprint version?
This ROM is built for the international variant of the m7. I prefer not to support devices that I don't possess, sorry about that.
Got Sweep-2-Sleep, or DT2W ?
purezalbert said:
Got Sweep-2-Sleep, or DT2W ?
Click to expand...
Click to collapse
I can't remember for sure if sleep gestures are included in the customization app, but I think they're there.
Siphoné said:
I can't remember for sure if sleep gestures are included in the customization app, but I think they're there.
Click to expand...
Click to collapse
I am currently using Xenon HD's Marshmallow ROM and it has double-tap-2-wake, and status bar to sleep.
The main issue I have with the HTC one m7 is the fact that the power button is too hard to press with a case on, thus double tap 2 wake is much needed! It would be nice if it was possible to integrate these functions into the kernel, or if there was Any other way!
purezalbert said:
I am currently using Xenon HD's Marshmallow ROM and it has double-tap-2-wake, and status bar to sleep.
The main issue I have with the HTC one m7 is the fact that the power button is too hard to press with a case on, thus double tap 2 wake is much needed! It would be nice if it was possible to integrate these functions into the kernel, or if there was Any other way!
Click to expand...
Click to collapse
I do believe Beanstalk also has it, but I'm not sure either.
What you could try to do is to extract the boot.img from one of those ROMs' ZIPs and flash it with the fastboot. It contains their kernel, which have d2tw.
What's the difference between TipsyOS and OctOS?
purezalbert said:
What's the difference between TipsyOS and OctOS?
Click to expand...
Click to collapse
They are two different ROMs, by different developement teams.
OctOS is based on CyanogenMod, TipsyOS is based on Slim, which makes Tipsy a bit smoother.
They have different customization options, but they also have a lot of them in common. Tipsy have a bit more of them, though.
TipsyOS has more pre-installed apps than OctOS, some of them are pretty much bloat.
Gonna give OctOS a test, will report back!
GPS not detecting satellites
In-Call sounds work, but sounds for media (music, mp3, youtube, and etc.) does not work.
purezalbert said:
In-Call sounds work, but sounds for media (music, mp3, youtube, and etc.) does not work.
Click to expand...
Click to collapse
I had no problems when I tested it. Can you do a clean flash and test again. This sounds very wierd, the sources of this ROM are mainly from CyanogenMod, so there should be no major issue.
Are you using a variant of the m7, perhaps?
Siphonay’s ROM building project presents
Android Open Source Project + Substratum OMS (AOSP-OMS)
{
"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"
}
Description
AOSP-OMS is vowing to provide a full stock Android experience in addition of the powerful Substratum theme engine.
Status
This ROM syncs frequently with the latest releases of Google's Android sources.
Bugs
No bugs to report at this time
You can, and are encouraged to report any bug you encounter with this ROM. Will be taken into account reports containing the following :
The build you are using
Clear steps to reproduce the bug
Optional logcat of when the bug happens
If possible, tell me if you experience the same bug on another device with the same ROM
Of course, any other information you judge useful
When meeting this criterias and if other users approve your report, it will be added to the list. Bugs encountered with the use of Xposed or a custom kernel will be discarded.
Downloads
Android Open Source Project + Substratum OMS Built 19-10-2016 md5 sum: 13a7ce239c39bae1bc06262052e3ac02
The OpenGapps package is recommended.
Frequently Asked Questions
When is the next build coming?
I can't give precise information about the next build. I try to do a new build each time there is a significant change in the ROM's sources (bugfixes, new features...), but keep in mind that I can only do this on my personal computer for now, and that I also do it on my free time. So please be patient!
Will you fix this bug?
Unfortunately, I'm not the person in charge of fixing the ROM's flaws internally. We have to wait until the bug is fixed in the upstream sources (either CyanogenMod, or the ROM developers of the one in this thread), and that I do a new build.
Will a Nougat version of this ROM be available?
I hope so! Again, this depends CyanogenMod 14 ever comes to our device, and if the ROM developers carry on to this version too. I can't say for sure, but if it is possible, it will be done.
About the HTC One M7 ROM Building Project by Siphonay
As an effort to keep our device alive, I'm trying to build the various existing CM flavors not already officially or unofficially available for it to keep its ecosystem varied, and provide its user a wide range of choice for their device.
If you like this ROM, you should definitely check out the other builds of this project!
Unofficial Xperia Open Source Project (XOSP) - Unofficial Android Open Kang Project (AOKP) - Unofficial PAC-ROM - OctOS M Community Build - UNOFFICIAL Tipsy OS 4.9 - OctOS M Community Build - Android Open Source Project + Substratum OMS (AOSP-OMS)
If you'd like to donate to the project (p.e. to fund a server to automate the builds in the future), I'd ask you first to consider if you have anything else more useful for you that you'd want to do with your money. If you really want to help this way, you can send me money with PayPal.
Sources
Kernel source
Device tree
Device manifest
AOSP-OMS (previously AOSP-RRO)
Credits
CyanogenMod
AOSP-OMS
Substratum
Hello such, I have an error in the 2 roms ke and tested you is that when updating applications including SuperSU (not if it will be the cause) when you restart the phone stays on the screen bootamination and not passes that screen
antonio82 said:
Hello such, I have an error in the 2 roms ke and tested you is that when updating applications including SuperSU (not if it will be the cause) when you restart the phone stays on the screen bootamination and not passes that screen
Click to expand...
Click to collapse
That's wierd, does it do the same on other MM ROMs like ResurrectionRemix or Slim6? I never heard of that problem, and didn't experience it myself. Are you using Xposed?
Please try to provide me a logcat of when you are stuck on the boot animation.
Siphoné said:
That's wierd, does it do the same on other MM ROMs like ResurrectionRemix or Slim6? I never heard of that problem, and didn't experience it myself. Are you using Xposed?
Please try to provide me a logcat of when you are stuck on the boot animation.
Click to expand...
Click to collapse
I made a new installation and update all applications esra time if started without problems
Glad to hear it
hello that such I returned to happen what happened to me before you leave the log aki I've taken in recovery
Same request as in TipsyOS, can you please add DT2W feature? I use it all the time on XenonHD LP/MM roms.
Thanks!
Mate, I got to say... from all your builds, this is the most stable. A bit early to say, but for two days, no reboots, BT streaming to my car stereo working good, GPS working as it should. The only problem I faced at the beginning was the WiFi disconnection. I sort of fixed it by flashing Xenon HD's boot.img from the latest ROM. Now no WIFI disconnections and I also have stable performance playing Clash Royale, which it was constantly crashing in other MM ROMs, including your PAC one.
AOSP-OMS + Xenon HD's Boot.img = WIN!
Let's see how it goes during the weekend.
Cheers!
Thanks for the tip Acogu!
Can you check if DT2W works with Xenon's kernel?
I think the problem is to use the substratum
shpitz461 said:
Thanks for the tip Acogu!
Can you check if DT2W works with Xenon's kernel?
Click to expand...
Click to collapse
I'm having only Sweep to wake/sleep under the Wake menu. On the Xenon ROM file's name it says S2W so don't know if that version only has that feature.
Maybe you can check with the previous release.
?
I see. I'll give it a shot, thanks!
shpitz461 said:
I see. I'll give it a shot, thanks!
Click to expand...
Click to collapse
So is it working? Is it more stable/faster than xenonHD?
I actually just flashed it now, having some issues, but will give it a day or so and see how it is.
DT2W is enabled and works (after flashing the boot.img from Xenon). Still need to test everything (GPS, bT, etc...).
Cannot install Android pay. Any solution, thx
skyers13 said:
Cannot install Android pay. Any solution, thx
Click to expand...
Click to collapse
Please provide me more information about you problem. xxx doesn't work doesn't help me diagnosing anything.
Do you have a "cannot install app" error? Does the app crash when you launch it?
Siphoné said:
Please provide me more information about you problem. xxx doesn't work doesn't help me diagnosing anything.
Do you have a "cannot install app" error? Does the app crash when you launch it?
Click to expand...
Click to collapse
If it's just safetynet, then it is a known issue.
Sultanxda found a workaround for that.
It was on the front page of xda recently.
https://github.com/sultanxda/androi...mmit/abc05b16bbd33521c2fffaf491c5657a94bfcfc5
FeelThePoveR said:
So is it working? Is it more stable/faster than xenonHD?
Click to expand...
Click to collapse
shpitz461 said:
I actually just flashed it now, having some issues, but will give it a day or so and see how it is.
DT2W is enabled and works (after flashing the boot.img from Xenon). Still need to test everything (GPS, bT, etc...).
Click to expand...
Click to collapse
It works perfect!
Tested GPS, BT audio streaming, BT phone, DT2W works out-of-the-box when you flash Xenon's kernel, Substratum works great, great job!
DND with alarm worked great.
I've never had any stability issues with Xenon (used LP though, not MM, didn't like the MM build, had a few annoying bugs).
Going to see how battery life is in the next few days.
Not sure if this can be fixed, but the BT volume resets to MAX every time I'm connecting to the car, and the music is blasting On LP it would remember the last BT volume.
in google play, it displays the app is not compatible with my device. I can't install it to my phone.
skyers13 said:
in google play, it displays the app is not compatible with my device. I can't install it to my phone.
Click to expand...
Click to collapse
That's not the ROM's fault, then. If I recall right it won't install on rooted systems, unless you got the .apk and a workaround to make it work. I can't help much with that, sorry.