[ROM][ALPHA][9.0.0] Slim9 [ocn] - HTC U11 ROMs, Kernels, Recoveries, & Other Develo

SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet 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 our public Gerrit to submit patches of any type.
Slim9 is the project name for SlimRoms based on Android 9.0.0 Pie and offers the following original features:
TBC
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - ocn kernel source.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
XDA:DevDB Information
SlimRoms u11, ROM for the HTC U11
Contributors
Flinny, Slimroms
Source Code: https://github.com/slimroms/device_htc_ocn
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: Slimroms
Version Information
Status: Testing
Created 2018-10-16
Last Updated 2018-10-27

How to install.
You're likely to have to fully wipe and fully format the data partition again.
I have been using Open Gapps for testing (ARM64 pico variant)
If you don't follow the above I can't help you
What works
All of the main stuff.
Calls
Camera
GPS
Bluetooth
Wifi
NFC
What's still to do.
It's basically AOSP at the moment, there are no real customisations yet, they will come... but no ETA!
Gestures/Squeeze etc see above.
What doesn't work?
Probably lots of things I don't use... You tell me...
Changelog
Alpha 1
* Initial Release
Alpha 2
* Audio fixes
* USB tethering should work
* Started working over sepolicy
Alpha 3
* November security patch
* Selinux enforcing
* Probably other stuff...
Alpha 4
* December security patch
* fixed a couple of sepolicy denials (thanks The_Walking_Playground,ValKyre for testing)
Alpha 5
* Tweaked the auto brightness settigns (quicksettings bar should behave now)
* Disabled Interaction boost for now, there were some strange times it was sticking.
Alpha 6
Re-enabled interaction boost
Advanced reboot menu.
Alpha 7
January security patch
Switched to Tomascus's new kernel (non-EAS version)
Merged a big chunk of Tomascus's device tree changes. (see Here)
Alpha 8 *READ CAREFULLY*
Time has been short recently, so other than merging in the March security update basically all of the device updates and kernel updates are from Tomascus (unofficial lineage builds)
I had a strange issue dirty flashing this myself, It had been flashed over a couple of hundred times in testing... all of the settings categories were all jumbled up, no amount of clearing cache/deleting app data seemed to fix it. A clean flash did. It may have only been me, just be aware.
March security patch
Switched to Tomascus's EAS Kernel
Device tree updated with many of Tomascus's changes
Alpha 9
April security updates
Synced more stuff from Tomascus/updated kernel to latest see device tree etc.
Not sure if the settings issue going between alpha 6->7 is still there as I ended up wiping.
Downloads
Alpha 4
Alpha 5
Alpha 6
Alpha 7
Alpha 8
Alpha 9
I'm running this, but obviously, use at your own risk... (I still recommend a backup before flashing new versions)

I’ll use this post to note the reported bugs.
It helps when reporting bugs to follow the Bug Reporting steps:
https://slimroms.org/#/support/report-bugs
Make sure you have properly installed ADB
Plug your device to your Computer
Open up a command prompt on your Computer
Type the following (without the quotes): “adb logcat -d > logcat.txt”
Click to expand...
Click to collapse
Either attach it to your post or report it via the above link.
1. Android Auto – Blank screen when unlocking. No audio. Possibly relates to reported issues with Google Play Services and seems to relate to Android P, not this specific build. Fix is said to be incoming.
2. Issues with SIM2 – Flinny only has a single sim device. Please report these issues with logcat so they can be looked into.
3. Brightness slider – Works from 50-100% Under 50 shows no difference. Can confirm this, but at 50% it is at its lowest.
4. OK Google – For me, and many others obviously, OK google does not work or is grayed out. I flashed this https://androidfilehost.com/?fid=385035244224414620 in TWRP and it is back to working.
5. 3.5mm adapter – It appears it may be a kernel issue and is being looked into. Works a few times then requires reboot to fix.
6. Random reboots – I have just noticed that if adaptive brightness is turned off, it will freeze randomly. Sometimes its within minutes, sometimes an hour. Ill gather a log or two when I can.
7. Audio issues - Seems to be a codec issue. I use vlc without issue. Seems streaming services work fine.

miffymiffy said:
Different to what you sent me?
Click to expand...
Click to collapse
yes....

Great news flinny thx
But I can't seen to find pie ROM link ?
Link in second post don't seem to work?

spoonymoon said:
Great news flinny thx
But I can't seen to find pie ROM link ?
Click to expand...
Click to collapse
Needed a quick rebuild to change one last thing... the link will be in the 2nd post once I've tested it.

A build is up, see the 2nd post.

Works great, you are the best thanks

All the previous issues are fixed! Good job mate. I've been running it for a week and have not found anything rom related wrong. I am dual sim too.

miffymiffy said:
All the previous issues are fixed! Good job mate. I've been running it for a week and have not found anything rom related wrong. I am dual sim too.[/QUOTE
My stock ROM have mobile network standby cause battery drain , This 9.0 rom have too? I am dual sim too.
Click to expand...
Click to collapse

Kudos @Flinny. Will give this a whirl during the weekends as it requires full format data partitions. Awesome mews ??
Sent from my HTC U11 using Tapatalk

The dark theme isnt working for me. Other than that this rom flies!

Everything seemed to be working but dark theme and WiFi calling is not working on T-Mobile. You can turn it on but it doesn't do anything. Pretty snappy though, look forward to trying this full time when WiFi calling is working, that is if it ever works. =) Great job @Flinny

Volte not working
---------- Post added at 09:13 AM ---------- Previous post was at 08:40 AM ----------
Not supporting the quick charge

pradyumna2009 said:
Volte not working
---------- Post added at 09:13 AM ---------- Previous post was at 08:40 AM ----------
Not supporting the quick charge
Click to expand...
Click to collapse
It means slow charging?

Normal fast charging seems to work, Qualcomm quick charge on the other hand is the same as it was on my Oreo builds. HTC did something strange with it on stock...
Sent from my ocn using Tapatalk

How to activate the gesture?

Martinodanada79 said:
How to activate the gesture?
Click to expand...
Click to collapse
Read post number 2....
Sent from my ocn using Tapatalk

Flinny said:
Normal fast charging seems to work, Qualcomm quick charge on the other hand is the same as it was on my Oreo builds. HTC did something strange with it on stock...
Sent from my ocn using Tapatalk
Click to expand...
Click to collapse
What about volte ? Will later builds support volte?

Thanks for all your work.
The ROM feels great, but there's one problem:
The capacitive hardware navigation buttons won't react toward long press (including home button).
Which means I can't access Google assistant by home button, and can't split screen by recent button.
I'm using Buttons Remapper to solve it somehow.

Related

CM10.2 AT&T/TELUS UNOFFICIAL

THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your ONE X+, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
http://forum.xda-developers.com/showthread.php?t=2074396
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
[ROM] CM10.2 AT&T/TELUS , ROM for the HTC One X+
Contributors
Lloir, h8rift
Source Code: https://github.com/evitareul
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-11-28
Last Updated 2014-11-19
List of stuff that IS working currently (not released and no eta)
Display
Audio
MTP
Camera
Microphone
GPS Borked
Ril\GSM
WIFI Now borked
Bluetooth
NFC​
Reserved
CHANGELOG
Code:
18/2/14
Fixed call audio, all it was, was a super hard to find error which said which permission it was
Fixed Data\gsm
28/11/13
inital testing release
In call is 100% buggered
GPS is trashed
Camera works (if gps is turned off)
Most recent CM source
PLEASE enable the Xda 2013 theme to view this thread correctly, as it is a DEVDB thread.
which enables you to see the downloads section
Q&A
Bug reports
Reviews
Screenshots
ALL questions > Q&A and NOT into this thread
Bug reports > Bug reports tab, with a logcat
Once all the kinks are sorted, this will be pushed to OFFICIAL CM.
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
sledgeharvy said:
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
Click to expand...
Click to collapse
yes please ALL bugs, please make sure you have the xda 2013 theme on (bottom left corner on the site) so you can see the bug report tab. Also you will be able to see the Q&A section CM10.2 ATT thread, where you can ask questions
all questions should go to that section please
thanks
Data/WiFi working great (no lte here so can't test), messaging too, and whole ROM seems to be running very smoothly. Almost faster than stock I'd say and the phone seems to run at about the same temperature - though not as hot as usual when using a lot of data. Didn't encounter any unmentioned bugs and not had any crashes in my day of use, seems pretty stable. Nice job Lloir, honestly the only thing keeping me from using this is the call/audio issue. You've got an awesome start here, thanks for all the hard work!
guys please use the Q&A section or even the review tab (you need the XDA 2013 theme on)
thanks
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
loftwyr said:
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
Click to expand...
Click to collapse
Updates will be posted by the OP. FYI, that's a no no question too. Rest assured lloir is working on it unless otherwise stated by lloir.
Sent from my HTC One X+ using XDA Premium HD app
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Lloir said:
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Click to expand...
Click to collapse
is there a link to the leak??
TheJokah said:
is there a link to the leak??
Click to expand...
Click to collapse
if you can get access to my pc? sure, but i'm not going to be the target of a HTC c&d notice
short answer no.
Keep us updated. So excited!
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Lloir said:
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Click to expand...
Click to collapse
Still running Solomon's PA 4.2.2 build from Feb 19th. I'll assume I'm using the old hboot, then, so I'll try the build when it's posted!
Having a few issues with ril (data/gsm) at the moment, along with WIFI
the plus side looks like GPS is fixed, but can't confirm it 100%
more soon
don't go quoting this damned post here, but post in Q&A
Working as of now:
Camera
Video Camera
GPS (not sure if 100% yet)
GSM
Audio
Lights
Touch Screen
BT
MTP
Borked :
Not tested in call audio yet
WIFI (50% borked)
DATA (Kind of, doesn't connect to the interwebs)
SELinux (will be the last thing i fix)
Dialer app (phone.apk)
Thread Cleaned and Members please report vice posting against others, and I will ask any & all to watch their language, regarding profanity.
Thank You.

[ROM][Official][5.1.1][Nightly]CyanogenMod 12.1 Nightly for Huawei G620S,Honor 4/4X

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Official CyanogenMod Wiki:https://wiki.cyanogenmod.org/w/Cherry_Info
Important information:
This thread is for official CyanogenMod 12.1 builds for Huawei Honor 4/4X (Qualcomm version). The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Baseband requirement:
Your must install a compatible baseband before CyanogenMod can be installed, or you won't be able to disconnect a call.
Just flash via recovery, you only need to perform the action once
Che1_L04
Che1_CL10
Che1_CL20
C8817D
G620S_UL00
G620S_L01
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_cherry
Bug report: https://jira.cyanogenmod.org
Features:
Kernel based on official kernel source for Honor 4C(MSM8939), ported to MSM8916, update necessary drivers to QCOM lolipop baseline, and update from v3.10.28 to v3.10.49.
Many vendor blobs kang from rendang
Init scripts from Qualcomm's latest baseline: LA.BR.1.2.4-02710-8x16.0
Use open sourced charger
Set minium screen backlight to 5
Fix CPU Hotplug
Enhance Wifi signal strength (credits: @surdu_petru)
Fix multi-color battery & notifiction LED
Fix FLAC playback for some third-party players
Enable MTP by default
Add call recording
Add support for F2FS
Add PCC calibration interface
Add vibrator intensity control
Add double-tap-to-wake
Add glove mode
Add HW-based crypto support
Update CPU gorvenor driver from Qualcomm
Update thermal driver from Qualcomm
Update kernel scheduler and related syscalls (sched) from Qualcomm
Update memory manager from Qualcomm
Update lowmemorykiller from Qualcomm
Update bluetooth blobs from rendang
Enable KSM
Merge a bunch of kernel updates from Qualcomm baseline (see kernel commit for details)
Set SELinux to enforcing mode
If your device have an official lolipop port, please install that before install this CM port.
Supported devices:
C8817D
C8817E
G621-TL00
G620S-UL00
G620S-L01
Che1-CL20
Che1-CL10
Che1-L04
Installation:
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery, e.g., my TWRP with F2FS support: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-7-0-touch-recovery-t3199386
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Optional: Install the Google Apps addon package. OpenGAPPS recommended
Reboot
Download:
http://get.cm/?device=cherry
Credits:
Code Aurora Forum
CyanogenMod Team
surdu_petru
EloYGomeZ
ivan19871002
syhost
zhaochengw
mandfx
cofface
XDA:DevDB Information
CyanogenMod, ROM for all devices (see above for details)
Contributors
dianlujitao, surdu_petru
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: No Longer Updated
Created 2015-09-17
Last Updated 2016-02-14
Reserved
@Madhunath Already get solution for your device, read the thread and you'll find it
Thank You it's Really work full (Call hanging up issue Fixed) for Our Device Che1-L04.. :good:
dianlujitao said:
@Madhunath Already get solution for your device, read the thread and you'll find it
Click to expand...
Click to collapse
where is the solition dear?
Bug which i found
In MX Player if we Play any Videos then it's play good without any issue But if we Changed HW from SW then that Videos get reflecting like a light.. Hope it'll fixed in next build..
Request for a features !!!!
I Request you to can you please add Screenshot tile on Quick Setting Panel.. As we need to Press every time Volume Up + Volume Down Key for taking Screenshots.
Alternatively we can enable Screenshot Option from Settings> Buttons> Power menu.. But for this also need to Press Power Key. I want it on Quick Setting Panel.
Hope u'll add this features soon. Or if it can be enable by editing build prop then also let me know. How can i get this Screenshot Option in Quick Panel Setting as you mention that this Official CM12.1 doesn't Support any tweak or Xposed.
Thank You :good:
When we need to flash the baseband recovery , after wiping the data or before wiping data
Sent from my Che1-L04 using XDA Free mobile app
Raju Mondal said:
Thank You it's Really work full (Call hanging up issue Fixed) for Our Device Che1-L04.. :good:
Click to expand...
Click to collapse
How to fix call hanging issue?
Bharadwaz said:
When we need to flash the baseband recovery , after wiping the data or before wiping data
Sent from my Che1-L04 using XDA Free mobile app
Click to expand...
Click to collapse
Directly flash it.
wiping or not doesn't matter
Madhunath said:
How to fix call hanging issue?
Click to expand...
Click to collapse
Read the thread, baseband requirement part
Now G620S-L01 users can enjoy the nightly builds.
Follow the instruction, flash a suitable baseband, you won't get the dialer issue
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
bmasgone said:
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
Click to expand...
Click to collapse
The modem require only one installation, should be enough ( this will solve issue regarding Dialer, from some devices ) !
CM OTA flash only /system , /boot ( /recovery if you want ) partitions - so, modem partition will not be modified when you install a new update .
I just made a backup from my stock modem partition, just in case cannot receive officially Huawei OTA update .
Best regards !
bmasgone said:
I dont know why some issues are not mention in official CM bug report:
1. Audio totaly destroyed/not usable if ringtone volume is higher (AudioFX does nothing to speaker, not tested with headsets);
2. Compass not working - HERE IS how One Plus developer called Sultanxda, resolve the issue few weeks ago.. May be would help for our device too;
3. When forward youtube videos there is another issue - video stopped and needs to be reload;
Seems like everything else work as is...
PS: Does the modem needs to be one time installed to receive OTA updates, or every time when G620S-L01 receive update, the modem needs to be flashed again?
Click to expand...
Click to collapse
1: Will be fixed in the next cm nightly
2. can be fixed as long as huawei release lolipop kernel source
3. I've no idea
only need to flash baseband once
dianlujitao said:
2. can be fixed as long as huawei release lolipop kernel source
3. I've no idea
Click to expand...
Click to collapse
2. Very bad news. As my previous expirience with Huawei, should be miracle if officlialy update their phone even once.. what about sources..
3. @surdu_petru says in his thread, that already have solution and know how to fix the issue .. I hope you could include his fix to your release..
surdu_petru said:
I just made a backup from my stock modem partition, just in case cannot receive officially Huawei OTA update .
Click to expand...
Click to collapse
Would you share this with us, because I already flashed to test the Nightly with G7 modem..
bmasgone said:
2. Very bad news. As my previous expirience with Huawei, should be miracle if officlialy update their phone even once.. what about sources..
3. @surdu_petru says in his thread, that already have solution and know how to fix the issue .. I hope you could include his fix to your release..
Would you share this with us, because I already flashed to test the Nightly with G7 modem..
Click to expand...
Click to collapse
2. Already have official lolipop beta for honor 4x, when they release it, kernel source comes
3. I don't know about it
dianlujitao said:
3. I don't know about it
Click to expand...
Click to collapse
surdu_petru said:
About YouTube, I know how to fix this issue ... maybe I'll fix in the next update .
Click to expand...
Click to collapse
I hope there is a time to fix it before next release .. Higher Volume Ringtone + Youtbe fix .. and will remain just Compass when as you said Huawei release official sources .. :good:
bmasgone said:
I hope there is a time to fix it before next release .. Higher Volume Ringtone + Youtbe fix .. and will remain just Compass when as you said Huawei release official sources .. :good:
Click to expand...
Click to collapse
I decreased speaker volume to avoid boom, and increased voice call volume
Thank u so much for the Official CM, got a working and almost stable rom after a long wait, some issues found are
1.poor recieving of wifi signal, need to be closer to router to get proper signal
2.loudspeaker volume is very less usually when activate loudspeaker during a call and while playing recorded voice, whatsapp voices etc but playing music and videos are fine
3.Mobile data is not very stable, some time its not connecting even if its on
4.Camera clarity is low compared to stock camera, yellow colour appears all over the image while click using flash
One question> when new update comes in about phone> cyanogen update it download all 255mb file, is it possible to get only update file as ota?
Sent from my Che1-L04 using XDA Free mobile app

[ROM][Unofficial][CM12.1][BETA][Indonesia Developer ROM][9/30/15]

I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.

[20180521][UNOFFICIAL] CM12.1 for Mad Catz M.O.J.O

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
As active user of the MadCatz MOJO, I found it pitty that rom development halted, mainly because the Android-TV rom from Unjustified Dev has some limitations.
As a result I've done quite some reading on "how to create an android rom from source" in the last 4+ weeks, in the hope that I could improve the work of Unjustified Dev.
In my attempt to understanding building the android source code to create my "own" Android-TV rom, I was succesfull in creating my first CM ROM (took 2h30)
(Big thanks to the source on https://github.com/TeamRegular?utf8=%E2%9C%93&q=mojo )
changelog:
Code:
[B][U]cm-12.1-20171226-UNOFFICIAL-mojo[/U][/B]
- fixed media server crashes, audio is again functional :)
- included the Tegra note 7 - widevine L1 DRM libraries (testing required)
[B][U]CM-12.1-20171222-UNOFFICIAL-mojo[/U][/B]
- Fixed hardware identification
- added DRM libs to support for widevineDRM
[U][B]BUG [/B][/U]: No audio - mediaserver crashes :(
[U][B]cm-12.1-20171216-UNOFFICIAL-mojo[/B][/U]
- changed boot animation to google animation (I like it more then the CM one)
- changed default dpi = 240
- removed not functioning multi rom code
[STRIKE]- synced media profiles to be inline with ADT-1 and cm-13 tree[/STRIKE]
[STRIKE]- added google media_codecs_performance[/STRIKE]
- applied some cm-13 changes to sync tree.
[B][U]BUG[/U][/B]: Play store seems broken,
[U][B]cm-12.1-20171208-UNOFFICIAL-mojo[/B][/U]
- Included nvcgcserver - should fix chrome issues with streaming.
- Applied kernel patch to increase from 3.4.57 -> 3.4.59
[U][B]cm-12.1-20171203-UNOFFICIAL-mojo[/B][/U]
- The update is a minor Android build update : LMY48G -> LMY49J
- Security level set to November 2016
[URL="http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html"]http://www.androidpolice.com/android_aosp_changelogs/android-5.1.1_r36-to-android-5.1.1_r37-AOSP-changelog.html[/URL]
Location of the ROM:
Code:
File name : cm-12.1-20171226-UNOFFICIAL-mojo.zip
[URL="https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy"]https://drive.google.com/open?id=1SpF5dcRg7kHYstTQtGrTTzus4e7p6fAy[/URL]
File name : cm-12.1-20171208-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2"]https://drive.google.com/open?id=1ocMDgBCHDC4VV8rYBtEuQUHq81xhtSa2[/URL]
File name : cm-12.1-20171203-UNOFFICIAL-mojo.zip
URL : [URL="https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l"]https://drive.google.com/open?id=1KctTiSn8Hv8IiHGPZXDa7A_I4cDbZ29l[/URL]
Next step:
- fix issue : https://forum.xda-developers.com/showpost.php?p=69887922&postcount=393 the post should contain enough info
- gaining more ROM development skills
- build AndroidTV-5.1 rom or CM13
Side note: I'm not as experienced as Unjustified Dev, so a "mayor" update can take a while,
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Mad Catz M.O.J.O.
Contributors
carp_be, EdoNINJA93
Source Code: https://github.com/dide0
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Current Beta Version: 5.1.1_r37
Beta Release Date: 2017-12-03
Created 2017-12-04
Last Updated 2018-05-21
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Wmapa said:
CM13 would be very nice. I was trying as well but my skills are to low for + no time
( i'm from Belgium 2 btw )
Click to expand...
Click to collapse
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
carp_be said:
Same here only time in the weekend to do some stuff. I hope to release a new build on sunday
Click to expand...
Click to collapse
Will you work on cm13? It is way better than android tv if we use toplauncher it is very tv friendly
Thank you so much, OT!
Yeah, I also would prefer a Marshmallow or Nougat based ROM, since you can do more stuff with them and you can get an Android TV experience whenever you like by simply using 3rd party launchers.
Keep it up the good work!
Main fixes I'd like to see:
- Chrome fix (I know you just have to put a separate file inside a specific folder, but it would be better to fix it by scratch by installing a fresh new and optimized ROM)
- Netflix fix
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
New release
cm-12.1-20171208-UNOFFICIAL-mojo now available As I don't have Netflix/Amazon , please let me know if the this new build fixed the streaming issues in Chrome. I checked the forum posts, they mentioned setting the permissions on this file. I check the source code and this should be done by default in the building process.
While I expect the nvgcserver/Chrome fix would be baked in eventually, I think perhaps you are expecting a bit much of this poster's already-declared skill set when it comes to fixes. I'd love to see these things fixed (especially the WiFi bug - urgh!), but I'm not pressuring the individual as it is obviously just a nice weekend pass time for him/her.
However, good luck and I look forward to what comes next if it becomes possible for you. Clearly there are one or two of us MOJO faithful still keeping an eye on developments. Keep us posted. I'm pretty sure folks will perhaps send a donation or two your way if things do become viable for you.
Click to expand...
Click to collapse
thanks
For me it's indeed a hobby project for the weekend, I really like programming but besides writing some simulation software for work projects, I'm not in the programming/embedded development business. I already did a lot of reading in the Github changes/commits on the ADT-1 (molly) and TeamRegular repo's. It should be possible to create a CM13 rom as the ADT-1 has a working rom, CM14 is not working atm on the ADT-1 so I don't expect that I could provide such update.
Currently I'm focusing on the CM12.1 branch as there is a working "rom" (see above ) and trying to add Android TV on this. The ADT-1 has such ROM, so it must be possible on the MOJO. I'm busy merging the changes from ADT-1 to MOJO but atm my build is stuck in a boot loop.
- Wi-Fi activation fix (on both CM 12 and CM 12.1 for Mojo the Wi-Fi activation works randomly after you boot the device and you have to restart the console everytime it doesn't)
Click to expand...
Click to collapse
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
carp_be said:
On which ROM do you have this problem ? I only have the AndroidTV ROM installed on my mojo and I didn't see this issue.
Click to expand...
Click to collapse
I have experienced this on both CM12.1 and Remix OS. Two things can happen:
Firstly, if you are using an SD card in your MOJO and you have this plugged in at boot, it's a lottery as to whether or not the console will boot up with any WiFi. I'm no expert at all, but by this I mean that it appears that the WiFi module doesn't even load into the system. It cannot be turned on or off as it is all greyed out. As I say, this doesn't happen on every boot up, but is very annoying when it does.
Secondly, if you decide to fix this by not using an SD card in your MOJO, the WiFi will be better but still not great compared to the stock OS. Sometimes it never connects on fresh boots, meaning I have to go into WiFi settings and switch off and on again several times before it connects properly. Then on other times very odd things happen when it does connect. For example, quite often I have experienced when downloading big app updates for example, it seems to "flood" the WiFi if that doesn't sound silly, which results in every one in the house complaining that our router has kicked all their devices off the WiFi and they can no longer get any connection. The MOJO itself also disconnects when this happens. The only thing I can do then is to reboot the router.
I am assured none of these things happen on the stock OS.
Good luck with your builds. I myself would love to see CM13, as I use a modified TV Launcher to polish things off. My fear with the Android TV system is it won't recognise my 2TB external drive, which would mean I couldn't use it. Remix had issues with it also. CM12.1 has no problems at all mounting it and allowing me access to my media files.
Great work ! Tested - nothing broken
Keep going !
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
EdoNINJA93 said:
It happens only on both CM12 and CM12.1 roms for the Mojo.
I think the issue is kernel related, but I could be wrong.
Click to expand...
Click to collapse
I've not seen this on the AndroidTV build of Unjustified Dev, so i'll diff it once with my build and see if there are driver changes.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
Could you please provide a feedback about Netflix and Wi-Fi issues?
carp_be said:
no luck today with AndroidTV, did several builds but after Android boots and optimizes it's App's and then it got stuck in starting the App's . I've not found a way yet to read out debug info during boot, so i'll invest some time on that subject. Next weekend the hunt continues.
Click to expand...
Click to collapse
Replace
Code:
persist.sys.usb.config=none
by
Code:
persist.sys.usb.config=adb
in default.prop and build.prop, this will enable usb debuging during boot.
rahsoft said:
Great work ! Tested - nothing broken
Keep going !
Click to expand...
Click to collapse
More info plz!
Is WiFi any better? What apps do you use?
K-Project said:
More info plz!
Is WiFi any better? What apps do you use?
Click to expand...
Click to collapse
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
rahsoft said:
I dont use Wifi - I use ethernet. Heard that Wifi works better without microsd in slot...
From what I tested - everythink works like before. I mean no new bugs
Some programs and Youtube on some videos just silent closes.... But this was on all CM 12.1 builds for mojo. Sound volume bug is still here but it is not critical.
Is it any way to add ethernet interface / config settings ?
P.S. Programs used: HD VideoBox, Torrent Stream Controler, MX Player, VLC, Archos Video player (for SPDIF), Youtube, Chrome, Total Commander, Simple Reboot, Set Orientation, SuperSU and so on...
P.S.2. Maybe it will be better set dpi to 240 in build.prop by default...
Click to expand...
Click to collapse
The playback issues could be related to DRM content. I saw that the CM build don't have the "google widevine" libraries included, while the AndroidTV build has. I'll include this in the next update,might solve the issue. Otherwise If you get a logcat file, the exception thrown by the app could shed some light what is needed.
besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
DPI can be changed to 240, will do (need to adjust ro. sf.lcd_density in system.prop file) .
Log
View attachment 2017-12-12-17-54-04.txt
Made little log - maybe will help
Please look at:
Process com.google.android.youtube (pid 10272) has died
Process com.lolapp.lolapptv (pid 22409) has died
Process ru.norgen.homevideo (pid 26606) has died
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="1980x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="1920x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
K-Project said:
Unless I'm going mad, which is quite possible, both those lines are exactly the same!
Click to expand...
Click to collapse
carp_be said:
...besides this I think there is a "bug" in the "OMX.Nvidia.h264.encoder" configuration. currently it's
Code:
<Limit name="size" min="48x48" max="[COLOR="yellowgreen"][B]1980[/B][/COLOR]x1088" />
, while ADT-1 has a "lower" resolution specified...
Code:
<Limit name="size" min="48x48" max="[B][COLOR="YellowGreen"]1920[/COLOR][/B]x1088" />
I don't know what the effect of the type is but I'll adjust it to in the next build.
Click to expand...
Click to collapse
Are you sure?

[ROM][UNOFFICIAL][LOS][8.1] crDroid 4.7 [NOTE9][Exynos][19.10.2018]

crDroid ROM for the Galaxy Note 9
What is this?
crDroid based on LOS for Galaxy Note 9. Based on Android 8.1
What's working?
Mostly everything, including dual speaker.
What's not working?
MTP - I've implemented a fix, just need to build again.
Powering off - if you power off your phone completely the rom won't boot. You need to go to trwp and reboot to system to get back in.
Let me know of any other issues.
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build linked below
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs). Even better if you have nothing to loose and wipe system,data,cache,storage etc
Flash the latest build (and gapps). GAPPS ARE NOT INCLUDED
Reboot and enjoy
Changelog:
19.10.2018- Initial Release
Downloads:
Galaxy Note 9 Exynos:
ROM Mega
ARH6 Vendor Required
Providing feedback:
Please feel free to provide feedback. We're trying to squash out as many bugs as possible.
JOIN OUR TELEGRAM GROUP!
https://t.me/joinchat/E_rQyU__5M_5wph6FrnpKA I'm under the name CodeFox if you need help.
Credits:
crDroid: It's their ROM.
Rainbow_Dash & malinathani: 90% of Credit to them for helping me put the build together and linking me to sources.
Vaughnnn: For his Device Trees in GitHub
Ivan: Helping me Seal the Deal. (Get him Recognised Seal status pls)
tylerr: First tester, came up with the solution to power off problem. Thank you.
Iqbal Sareem: ROM God.
Changelog:
19.10.2018 Initial Release
XDA:DevDB Information
[ROM][UNOFFICIAL][LOS][8.1] crDroid 4.7 [NOTE9][Exynos][19.10.2018], ROM for the Samsung Galaxy Note 9
Contributors
s3xxt0y, Rainbow_Dash, malinathani, jesec,Vaughnn,farovitus
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Vendor ARH6
Based On: crDroid, LOS
Version Information
Status: Testing
Current Beta Version: 1
Beta Release Date: 2018-10-19
Created 2018-10-19
Last Updated 2018-12-29
despacito
Rainbow_Dash said:
despacito
Click to expand...
Click to collapse
but shirley temple
Rainbow_Dash said:
despacito
Click to expand...
Click to collapse
Thread is copypasta from your thread if you can't tell. I couldn't be bothered to make it pretty tho
??
I've been using this rom for the past 12 hours. Very good. Haven't run into any issues other than the brightness bug but that's in Pixel Experience as well and you're using the same device tree so that is to be expected. (Brightness gets stuck at max once you set it at max and you have to reboot to make it unstuck)
Features are very welcome and rom is quite smooth overall. Definitely daily driver material. Really enjoying it. Appreciate your contribution to this device. I'll report anything else I find.
Thank you
Wow. I know Crdroid from one of my previous phones. Welcome
Nasty_z said:
I've been using this rom for the past 12 hours. Very good. Haven't run into any issues other than the brightness bug but that's in Pixel Experience as well and you're using the same device tree so that is to be expected. (Brightness gets stuck at max once you set it at max and you have to reboot to make it unstuck)
Features are very welcome and rom is quite smooth overall. Definitely daily driver material. Really enjoying it. Appreciate your contribution to this device. I'll report anything else I find.
Thank you
Click to expand...
Click to collapse
The brightness bug went away for me strangely. Turn on adaptive brightness and reboot and see if it goes away. Glad it's working well for you anyway. The only issue I've noticed is a bit of lag with the vibration motor when typing but turning off haptic feedback resolves that.
s3xxt0y said:
The brightness bug went away for me strangely. Turn on adaptive brightness and reboot and see if it goes away. Glad it's working well for you anyway. The only issue I've noticed is a bit of lag with the vibration motor when typing but turning off haptic feedback resolves that.
Click to expand...
Click to collapse
Just a heads up before moderators catch u the telegram link is forbidden on XDA.

Categories

Resources