Related
Well, I did it. Ported my number to T-Mobile. Poorer signal in some places, but I get consistent 4Mbps at my desk at work.
So.... I'm going to pretty much retire from maintaining this OP.
If someone wants to start a new thread with a similar format, go for it. If not I'm willing to come in here and try to do a quick update once in a while. It's not like things are moving as fast as they used to anyway, and the appspot changelog is great for displaying what is going on.
[HIGHLIGHT]Some Goodies:[/HIGHLIGHT]
With HDMI out there are some cool possibilites for the Evo. One of the best examples is in a thread started by Lokifish Mars: Use your Evo as a Desktop PC
There are tons of great theme engine themes. Many on the market and some only available on XDA. But since I'm a self serving biased jerk who unfairly looks out for his friends, I've got to mention the Sculpted theme from Shift. I loved Sculpted on CM6, but the version he created for CM7 is incredible, and all you have to do is grab it from the market, and then choose it in Theme Chooser.
Everyone's favorite something-goat-something-Shift-hater Karadorde dropped a little ray of nightly flashing sunshine in our lives. It's a recovery flashable script similar to Calkin's flash all that just flashes cache and dalvik for those times you've gotta have your nightly fix, but don't feel like setting everything up again. Check out his thread for instructions, and download the script there or here: nightly wipe zip
rstuckmaier has basically been doing my job for me recently, and created a thread just for CM7 fixes, tweaks, and work-arounds.
WiMax support is built into CyanogenMod 7. HDMI mirroring is supported in the kernel, but you will need an app to turn on mirroring. You can grab HDMwIn from the market. After trying it out, please support further TeamWIN projects by buying the donate version.
Quick Links:
Nightlies
Google Apps
Commit Log
DrMacinyasha's Mirror (CM and more)
Changelog App
CM Forums Evo Experimental
rstuckmaier's Tips Thread
TecherrataFiles Twitter - Mirror of releases
[HIGHLIGHT]New since 7.0[/HIGHLIGHT]See the Official Changelog at this link
7.0.2
Common: Fix issue with missing built-in themes
Common: Update bundled ROM Manager to latest version
Supersonic: Actually fix GPS
Supersonic: Fix proximity and light sensor
7.0.1
Common: Fix fling velocity of status bar and ADW swipe - Sven Dawitz
Common: Fixed webview layout bug (issue 3229) - Zinx
Common: Fix GVoice-opens-twice bug - Zinx
Common: Fix issues on all devices with DNS resolution failure after some time - Zinx, various
Common: RTL improvements - Eran Mizrahi, Eyad Aboulouz
Common: Fix crashes in Arabic locale - Eyad Aboulouz
Common: Add Arabic keylayout - Eyad Aboulouz
Common: Improve ADWLauncher scrolling/zoom performance - Pavel Kucera
Common: Fix excessive memory use when appending to textviews - Cyanogen
Common: New wallpapers from the CM community (CC License, see app for credits)
Common: Option to disable vibration while in-call - Evan Charlton
Common: Add long press option to status bar widgets for settings - Alex Avance
Common: Compact carrier and status bar tweaks - Nihanth Subramanya, rorifree
Sholes: Fix connectivity loss bug - cvpcs
Speedy: Fix keyboard lights - JD Horelick
Glacier: Fix backlights - Zinx
Glacier: fix GPS issues - Zinx/QCom
msm7x30: Fix bugs during video resume - Zinx
qsd8x50: Fix 720p video playback
qsd8x50: Unified 2.6.37 kernel - Cyanogen, toastcfh, slayher
Espresso, Legend: WiFi fix (HTC)
Supersonic: Fix GPS issues (HTC)
##########################################
Please bear in mind this is a nightly build, meant to be a testing ground for developers, and there may even be times the new nightly won't work at all. This is a common way of working in open source software. Most of the problems you are encountering the developers are already aware of. With that said, most of the nightly builds has been very solid and stable for many people here, and several of us that are used to development software are using it as a daily driver. Just realize that is not the intention of nightly builds.
[HIGHLIGHT]CM6 features not available & Bugs[/HIGHLIGHT]
Camera does not have touch to focus and some other features from CM6
Bluetooth Mouse cursor - BT mouse will connect, but acts more like a trackball. See the Use your Evo as a Desktop PC thread for a patch.
No 720p video recording
GPS often will not lock. Cyanogen said he is working on a fix for a point release. Basically the non-open source HTC drivers were used in CM6, but for CM7 they are using the open source reference drivers from the chip manufacturer. Something is strange or maybe even buggy about the Evo hardware. The good news is there is a workaround that has worked for most people.
Note - this is pasted from rstuckmaier's excellent tips thread
Make a Nandroid of your current CM7 setup.
Boot into recovery and perform a full wipe (or use Calkulin Format ALL zip)
Flash any Sense ROM
Open the Market and download MSL Reader, write down MSL.
Open Dialer/Phone and type ##4772579# (##GPSCLRX#)
When it asks you for a password type in your MSL
Reboot phone
BE OUTSIDE
Turn on GPS and open Maps, allow it to fully lock your location (may take a few minutes, do not just wait for initial lock).
Leave GPS on
Turn off phone, reboot into recovery.
Nandroid restore your CM7 backup
[HIGHLIGHT]Installation Info[/HIGHLIGHT]
You must be fully rooted (including NAND rooted)
Nightlies are posted at: http://buildbot.teamdouche.net/nightly/supersonic/
After flashing the main part of CM, you will probably want to flash the Google Apps Add-On, which adds the Market and allows you to download things like GMail, Goggles, Voice Search, and Maps. Gapps is available here: http://goo-inside.me/google-apps/
There are now only two versions of GApps, one for Tegra CPUs and one for non. For the Evo you want the standard version without Tegra support
GApps changed for CM7 and only has the basics for market access. When you first log in you will be given a screen of checkboxes to download the apps you want. You can also add them manually later from the market.
DrMacinyasha's goo-inside.me is the official source for GApps, and also mirrors most of the other content:
drmacinyasha said:
Just a heads up, I've been keeping my own mirror of all of the CM stuff for EVO. Useful for those who want the gapps updates but don't have an account on the CM forums, etc., and also has all of the Snap kernel files mirrored:
http://goo-inside.me/google-apps/
http://goo-inside.me/evo/cm6/nightly/
http://goo-inside.me/evo/cm6/rc/
http://goo-inside.me/evo/cm6/stable/
http://goo-inside.me/evo/cm6/snap-kernel/
I update the site whenever I can; it's not yet auto-updating, but I'm looking at a way to fix that.
Click to expand...
Click to collapse
[HIGHLIGHT]What features are included[/HIGHLIGHT]
Full AOSP
Running 2.6.37 Linux kernel
Android OS 2.3.3 (Gingerbread)
More standard Bluetooth stack. HTC uses a funky proprietary bluetooth implementation. Cyanogen has replaced this with a more common one, so the phone now supports HID (Mice & Keyboards) and the Wiimote app in the store.
Tons of Cyanogen Mod tweaks and tools, including but not limited to:
Updated music app with extra options and lockscreen controls
kernel speed tweaks
Notification Drop down power control
CyanogenMod Settings integrated into settings menu
DSP settings
T-Mobile theme engine
Torch flashlight uses camera flash, includes widget
Additional settings and tweaks for Contacts, Dialer, and MMS (maybe more)
[HIGHLIGHT]FAQ[/HIGHLIGHT]Q. When the new nightly comes out can I just download and flash over the top of the install?
A. Because these are development nightlies they are not guaranteed to work in this way. In many cases this may work fine, but even if it does it may not implement a new feature or fix. For example the MMS fix would not show up unless you wiped, or deleted a specific directory. However, this usually works ok.
Q. What has changed in the newest nightly build?
A. For me the easiest thing has been to follow the CM Source twitter feed. Pretty much any change that doesn't mention another device specifically will show up on the nightly.
Look here for Cyanogen's changes: http://github.com/cyanogen
and here for CyanogenMod in general: http://github.com/CyanogenMod
Q. Flash isn't working
A. Go to the market, search for "Flash Player" and install.
Q. I don't have a Market icon or any other google apps
A. You didn't flash gapps or flashed the wrong one
Q. Rom Manager won't let me download the nightly
A. Purchase the premium version from the Market
Q. Why is the launcher slow?
A. It isn't really, but the defaults used on ADW make it feel sluggish. Try some of the settings from this post by midri
Q. How can I update PRL?
A. There currently is not a way to do it in Cyanogen Mod. You will need to restore a nandroid backup of a Sense ROM (you did make one, right?), update the PRL, then Nandroid back to CM6.
Q. What times are the nightly builds? And what time in my timezone?
A. To my understanding, the bot begins building at Midnight UTC which is 8:00pm EST. They finish around 30 mins later. You can always check this link and verify that the mod date is the next day (for us in the U.S.) In otherwords, It's currently 10:50pm EST on 7/10 and the mod date on the zip file is 2010-Jul-11 00:35:56 so I know it has been built:
http://mirror.kanged.net/cm/nightly/supersonic/
Q. Rom Manager says there are no updates
A. Since these are nightly builds and not releases, the filename stays the same and Rom Manager knows you have a rom named that already. If you want to assure you have the latest, clear your download cache and re-download.
Q. Can I install the Sense dialer/music player/widgets/etc. ?
A. By default no. Sense widgets only work with the Rosie launcher. Most of the other stuff it tightly bound to the framework, which is why many of the AOSP applications can not be easily installed on a Sense ROM.
Q. Is there any way to run the stock android 2.3 launcher instead of ADW?
A. Search the market for "gingerbread launcher." There are several available for free.
Q. My notification toggles keep disappearing! Where did they go?
A. Often changing themes will cause this. Just grab the Notification Restart app in the market. It basically just kills the notification bar so it resets.
Please feel free to add any that I missed, but hopefully we don't get repeats of the same answered questions or known bugs. I hope this makes things easier for everyone to know what's going on.
Thanks again for your hard work, Cyanogen, Toast, #teamwin, and all of the CyanogenMod Team!
Thanks for the thread!
sent with evo 4g
HW 0003, and Nova panel.
I'm getting a green bar (graphical glitch) at the top during video playback.
Getting it on videos using the YouTube app, and also on some MP4 movies on my sdcard. Happens no matter what video player I use.
Oddly enough, videos that I had recorded with the Evo camera do not have this.
Is it just me? or anyone else having this issue also?
As far as the Facebook, I cannot add my facebook account. The first time it asked for info and appeared to work, but if I go back into Accounts it's not there and I can't seem to add it.
I downloaded Swype beta from the site and it's working fine for me.
Philosuffer said:
HW 0003, and Nova panel.
I'm getting a green bar (graphical glitch) at the top during video playback.
Getting it on videos using the YouTube app, and also on some MP4 movies on my sdcard. Happens no matter what video player I use.
Oddly enough, videos that I had recorded with the Evo camera do not have this.
Is it just me? or anyone else having this issue also?
Click to expand...
Click to collapse
Yup, same here, 003 with nova and seeing the green bar. But, mine switched between purple and green at first, then switching to just green. But weirdly,I've only seen the bar watching hq videos on youtube. Regular movies don't have that....odd.
Would it not be better to use a bug tracking software, even a free one to keep the info sorted?
also have green bar, hw3, novatek panel. don't have it in videos i've recorded. it may just be a function of the youtube app, nothing to do with cm
Another bug.
When you go to cm settings > input settings> haptic feedback tweaks > change any of the patterns ...cm settings force closes
Sent from my PC36100 using XDA App
Kllian said:
Would it not be better to use a bug tracking software, even a free one to keep the info sorted?
Click to expand...
Click to collapse
lol, they have one at cyanogenmod forum. which is probably where all this should be going anyway
HOWEVER, it isn't for nightly builds. you aren't supposed to be posting bugs there for nightlies
timothydonohue said:
lol, they have one at cyanogenmod forum. which is probably where all this should be going anyway
Click to expand...
Click to collapse
I don't think they do bug tracking for nightly's.
Sent from your moms EVO 4G
When the new nightly comes out can I just download and flash over the top of the install so I dont have to start from scratch tomorrow?
heres a question:
is there anyway to get the htc dialer app back on this rom, or is that part of sense, if so can you please link up a apk?
so does this mean that there will be a new build every night from now on or what.
Fring works on WiFi with no problems but FC's when on 3g.
Turn Exposure to +1 on front camera to make it not so dark.
dkotoric1 said:
so does this mean that there will be a new build every night from now on or what.
Click to expand...
Click to collapse
if i understand it correctly, it will be recompiled every night. however, if no code changes were made during the day, before compile, then the nightly won't be any different than the one before.
Also Exchange support in Froyo does not work reliably. This is not a bug in the mod, but in Froyo itself.
timothydonohue said:
if i understand it correctly, it will be recompiled every night. however, if no code changes were made during the day, before compile, then the nightly won't be any different than the one before.
Click to expand...
Click to collapse
Bingo. Changes may be EVO specific or may be generic to all devices. This is why nightlies are not reliable, they are simply a snapshot of the code at the moment. I read a comment that sounded like one of the changes made for the EVO broke the Droid build. Don't think of these as general use builds like we see from DC, Avalaunch, etc. When there is an RC or final, cyanogen typically will post that here.
needoZ said:
Also Exchange support in Froyo does not work reliably. This is not a bug in the mod, but in Froyo itself.
Click to expand...
Click to collapse
exchange is working perfectly for me?
CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone, tablet or PMP.
Code:
#include
/*
* 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.
*/
These are CM12.1 builds for the Hisense Sero 7 Pro (Enterprise, M470BSA). It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
GPL:
Code:
http://github.com/Meticulus/android_kernel_hisense_m470bsa
Warning: Currently, this ROM is in BETA
Download: meticulus.co.vu
Gapps here or here
I'm impressed. I have a Moto G 2nd Gen, which supposedly was one of the first devices to get Lollipop, but you beat them to it
NEW BUILD!
New build posted!
Mitigated a kernel issues causing lag
CM Sources update
Dude, thanks. Sero 7 and Dev's just keeps surprising me.
LOVE IT, minus one killer bug.
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work
Quickdraw996 said:
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work
Click to expand...
Click to collapse
My apologies for the sign up issues on my site. I believe I have them worked out and I have cleared your attempt so you can try again if you like.
NEW BUILD!
External SD fixed
SeLinux: enforcing
:highfive:
I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?
lichan said:
I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?
Click to expand...
Click to collapse
Hmm... S-on is an HTC thing isn't it? Like some sort of bootloader thing I think... Strange. Might be an Sepolicy issue.
I'll look into it... I currently looking into Apps2SD issues on another device ATM...
HTC and something else if I remember correctly.
Sent from my XT1023
A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.
AngryManMLS said:
A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.
Click to expand...
Click to collapse
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....
Meticulus said:
External SD fixed
SeLinux: enforcing
:highfive:
Click to expand...
Click to collapse
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)
Quickdraw996 said:
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)
Click to expand...
Click to collapse
Don't dirty flash this one, the selinux contexts will be messed up if you do....
Alright, thanks!
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)
Meticulus said:
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
Click to expand...
Click to collapse
True. It's a matter of optimizing code and what not I'm assuming.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
Click to expand...
Click to collapse
I'll try to get you a log in the next day or two. I've been busy working on a project on my Verizon Note 3 not to mention I'm still trying to find a recovery that will still let me restore back to my CarbonROM 4.4.2 backup. Seems like the newer recoveries aren't letting me restore back... very weird.
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
Click to expand...
Click to collapse
True true. I was more of less noting there being no theme support for those wanting to know more than anything else.
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....
Click to expand...
Click to collapse
I'll try to get you a log of Bluetooth use on my end alongside with the Titanium Backup issue.
And here we go...
http://www.androidpolice.com/2015/0...-built-lollipop-5-0-1-rolling-select-devices/
Official nightlies are coming out now.
NEW BUILD!
CM Sources update
Tweaks to Kernel for latency...
Feels snappier, but might be a placebo effect.
New bug/issue tracker on the download page. Please submit issues/bugs there. :good:
NEW BUILD!
BLUETOOTH FIXED!!!
Graphical Glitch in Navigation bar fixed
Missing schedulers in performance fixed
:victory:
Really want to try this but its my wife's tablet. So she won't let me. She doesn't want to loose everything on her device.
Hi all,
A while back I asked what you guys would like to see from a ROM and that never took off however I did take available suggestions to heart.
Let's start with a bit of background. In 2012, I was introduced to the whole concept of Android development. I rooted the device I had at the time, installed CM, and for a while everything was great. What I didn't like and still don't like about CM is that it is somewhat lackluster when it comes to features and what I didn't like about other ROMs at the time was that they had far too many. Eventually I gave AOKP a shot and its been a favorite of mine for a long while.
Jump to the present. I can do a lot more in terms of development, I can do things now that I had only dreamed of doing a few years back. I saw AOSParadox and the idea of a fully optimised AOSP ROM really appeals to me.
Meet AOKParadox: sheer optimisation and freedom without insane decisions, and the lack of features.
Here's the features I plan to use so far:
1. Compilation with the Uber toolchain (ready)
2. CAF applications and optimisations (Sultans drivers and SWE browser are what's planned)
3. Integrated flashtool (maybe flash fire)
4. Boeffla (with Swell-V6 as default along with my other profiles)
5. An Adblocker (thinking AdAway)
6. Aegis (no longer possible)
7. Xposed (I won't support those using it however)
8. ViperAtmos (Viper is ready however Atmos isn't)
9. Integrated SuperSU (Consider it done)
10. A custom HAL (ready for alpha)
11. Layers (will replace CMTE) (CMTE removed, need to find layers commits)
12. A dark mode (ready for alpha)
13. AROMA (... maybe, poses issues for some)
I plan to integrate most of these into the sertings menu. Note that a few of these features may not make it into the final product and I may implement other features... I have to ask permission of course. I can't just steal work from other developers
Any suggestions are incredibly helpful and if a developer would like, I would consider putting your work here too.
I'm going to start work bow and hopefully seed an alpha to those I trust in the coming weeks.
Suggest away,
RJ
Edit: I've realized that the developers of AOSParadox may feel offense due to the name I've chosen, and as such, AOKParadox will no longer be named. Suggestions are welcome.
Would it be posible to add support for cm13 themes or layers?. cuz that would be awesome.
elander said:
Would it be posible to add support for cm13 themes or layers?. cuz that would be awesome.
Click to expand...
Click to collapse
AOKP supports CMTE by default however I could look into layers instead
That sounds like a great idea! I would base your device tree of the CM one and the kernel also. I like that you want to use layers instead of CMTE
Maybe I can assist you in some things, but I'm not an android rom developer.
taaeem said:
That sounds like a great idea! I would base your device tree of the CM one and the kernel also. I like that you want to use layers instead of CMTE
Maybe I can assist you in some things, but I'm not an android rom developer.
Click to expand...
Click to collapse
Definitely. Considering CM uses CAF now I don't have much to do in that respect.. Maybe I'll pull in Sultans qcom drivers. Not sure they'll work yet though. Definitely going to modify the kernel a ton though.
Your assistance would be much appreciated. Thanks.
Although I mentioned modifying the kernel earlier, there is one I'd like to ask to implement. Not giving anything away, but I've contributed a little bit to it on the CM alpha side
Edit: I was just able to give you five likes on one post. Weird..
In my opinion it wouldn't have sense to change kernel cause the built-in one is optimized for CAF sources wich is the main feature of AOSParadox. AOSParadox team will also probably add full Layers support, gestures, an option to switch from hardware keys to navigation bar and a black theme in the upcoming build.
The features that I would like to see added in AOSParadox are:
- OTA updates support
- built-in Viper4Android
- built-in SuperSU
- built-in AdAway
- removed old and ugly AOSP apps like music or browser (this one possibly replaced by CAF browser)
- quick pulldown, notification LED control, long press recent button to open the last used app and customizable power menu (with advanced reboot)
- all these features well-ordered in settings just like CyanogenMod
- apps like Layers Manager, Super SU and Viper4Android integrated in settings
- duble tap to wake in settings without kernel adiutor workaround
Inviato dal mio ONE E1003 utilizzando Tapatalk
Diego98 said:
In my opinion it wouldn't have sense to change kernel cause the built-in one is optimized for CAF sources wich is the main feature of AOSParadox. AOSParadox team will also probably add full Layers support, gestures, an option to switch from hardware keys to navigation bar and a black theme in the upcoming build.
The features that I would like to see added in AOSParadox are:
- OTA updates support
- built-in Viper4Android
- built-in SuperSU
- built-in AdAway
- removed old and ugly AOSP apps like music or browser (this one possibly replaced by CAF browser)
- quick pulldown, notification LED control, long press recent button to open the last used app and customizable power menu (with advanced reboot)
- all these features well-ordered in settings just like CyanogenMod
- apps like Layers Manager, Super SU and Viper4Android integrated in settings
- duble tap to wake in settings without kernel adiutor workaround
Inviato dal mio ONE E1003 utilizzando Tapatalk
Click to expand...
Click to collapse
Oh, I won't be using AOSParadox as a base. I actually looked at their kernel and device tree and it doesn't differ much at all. It would be easier to just fork Ashwins and build from there. CM is CAF based now in this respect. Thru just lack proper qcom drivers. I'm going to see if I can implement Sultans drivers for the One. Obviously jot all of yyrm will work but its worth a shot.
OTAs won't happen. I'm sorry, but I have no way of hosting builds yet.
Layers manager will be implemented
The CAF browser is definitely going to be there
Everything else I've already mentioned and is available from AOKP.
Thanks for the feedback!
I misunderstood, anyway the OTA support isn't that important and your ROM looks promising. I'll give it a try when it comes out ?
Inviato dal mio ONE E1003 utilizzando Tapatalk
Looking good from the features
Just wanted to say that don't use Aegis because it creates lots of problems for apps such as ADM
And Xtreme music sound mod would be great in place of viperatmos
Adesh15 said:
Looking good from the features
Just wanted to say that don't use Aegis because it creates lots of problems for apps such as ADM
And Xtreme music sound mod would be great in place of viperatmos
Click to expand...
Click to collapse
Xtreme music requires SELinux to be disabled last I checked and I'm not one to really do that for more options in terms of equalization. I think Atmos and Viper should suffice. Thanks for the feedback. Maybe it will show up as an option in AROMA whenever I chose to implement it!
RJDTWO said:
Hi all,
RJ
Click to expand...
Click to collapse
Wow, I have no clue about the different ROM types (apart from Slimroms and miui) but one can only admire the level of effort that you are putting in to this! Looking forward to the rom, can't think of anything else than you already put on the list.
Thanks!
Unfortunately Aegis is no longer a possibility. I require special privileges to access specific repos on GitHub...
@RJDTWO Can you port Miui ?
Many users are waiting for Miui on onyx
RJDTWO said:
Oh, I won't be using AOSParadox as a base. I actually looked at their kernel and device tree and it doesn't differ much at all. It would be easier to just fork Ashwins and build from there.
Click to expand...
Click to collapse
Then why call it AOKParadox? :/
I'm here just to wish good luck with the project and say that it is an amazing idea
Not asking for any features in particular just giving you my thumbs up
Quasar said:
Then why call it AOKParadox? :/
Click to expand...
Click to collapse
Have a better suggestion? I'm open to names.
AOSwellP anyone? In honor of the profiles I make?
RJDTWO said:
Have a better suggestion? I'm open to names.
Click to expand...
Click to collapse
Any rules about the names? Things you really want to have in it, like AOK or Paradox? I just finished reading Ready Player One, so I have plenty of names and references
charliebigpot said:
Any rules about the names? Things you really want to have in it, like AOK or Paradox? I just finished reading Ready Player One, so I have plenty of names and references
Click to expand...
Click to collapse
It would be nice to keep AOK in the naming scheme however I'm open to anything really
I don't adding xposed would be a good idea. But it's me
Know issues:
1. Bluetooth toggle will not turn on
2. video codec makes first 10-15 seconds of video only green screen--(not noticed so much after install gapps and using chrome browser)
3. Camera not working
Resolved*
*testing phone had stock camera app disabled and was using open camera. With stock camera multiple crashes and unable to connect issue with camera. V3.5 has removed stock camera and added open camera to priv-app (preinstalled)
4. Microphone is also not working
V3.5 has fixed microphone.
5. video recording not working
V3.7 fixed video record for back camera only--also seems to have stabilized photo camera--(but still has crashed)
V-x-4.1 minor edits. Removed old renamed files. Removed apps and libs for fingerprint scanner. Swapped apns-config.xml from V21 to try get connection for more carriers. But it seems some devices are not able to even see imei from board V4.1 removed. Audio broken
x-v-4.6 has audio streaming partly functioning. Audio/ video plays some amount of time then stops. but will continues if playing through bluetooth. Further testing on speaker needed. Audio issue notIS present in FMRadio and unknown in phone. So far only in streamingMOST SOUND situations, like music apps and YouTube.
Also list of added apps primarily added for testing reasons
1. GPS test
2. AudioRecorder
3. File_Manager _es_file V3 (fewer ads)
4. OpenCamera
V5.0
removed extra fingerprint program, added MDDB folder (base band) trying to resolve 2 reports of lost IMEI on this rom. I have not had issue, so cannot confirm if adding these files has fixed problem.
V6.7-current beta
/system changes tracked on github
v6.7-or current /system
boot.img changes on github
https://github.com/mrmazakblu/Slim-port-boot-img
..
..
Install:
must have unlocked boot loader.
put rom file on sdcard and install with twrp =>Latest TWRP 3.1.1-0
you needs to install gapps.
http://opengapps.org/http://opengapps.org/
You need to enable navigation bar to get onscreen buttons.
settings >Navigation >Navigation bar >Enable navigation bar.
thanks to : @vampirefo this rom is ported from his build for the BLU Life Max
XDA:DevDB Information
Slim6 port for R1-HD, ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 's Blu Life Max SlimRom
Version Information
Status: Beta
Stable Release Date: 2017-06-16
Current Beta Version: x-5.0
Created 2017-06-09
Last Updated 2017-11-02
Thanks Great work I would like a RR.5.7.4
Enviado desde mi R1 HD mediante Tapatalk
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
meroher said:
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
Click to expand...
Click to collapse
there are 4 screen shots on the screenshot tab. But the look of any rom can be changes how you like with different launchers if desired.
Fixed the bugs except for the camera one.
New zip file in download tab.
Moved status from testing to beta.
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
vampirefo said:
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Camera Is Fixed*
I now have camera working on this slim port...
uploading built/port number 33 (X-3.3)
still needs small bug fixed, that will not screen cast to chromecast.
and first time I opened camera I did not have any on-screen navigation buttons(no way to exit camera). after some time buttons were available and next time it opened normal.
mrmazak said:
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Click to expand...
Click to collapse
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
vampirefo said:
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
mrmazak said:
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
Click to expand...
Click to collapse
Yes, ROM is built for 6737, R1HD and Life Max are almost the same phone, difference size, camera and 6737 instead of 6735.
Anyway good job.
Sent from my Life Max using Tapatalk
how is the performance vs stock with all bloatware removed?
deathblade200 said:
how is the performance vs stock with all bloatware removed?
Click to expand...
Click to collapse
Seems a little quicker on slim6
Great job, I like it
So is this a usable daily driver?
roboman2444 said:
So is this a usable daily driver?
Click to expand...
Click to collapse
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
mrmazak said:
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
Click to expand...
Click to collapse
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
roboman2444 said:
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
Click to expand...
Click to collapse
I do not think the camera fix here will help 7.
These lib files, "so" files, "blobs", call them as you will. Are still for Android 6 so , as I believe will not work on 7
mrmazak said:
Seems a little quicker on slim6
Click to expand...
Click to collapse
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
deathblade200 said:
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
Click to expand...
Click to collapse
They would be the same or about the same, a rom doesn't increase benchmarks, a custom kernel might, benchmarks have their place this isn't one of them.
To each their own I guess.
Sent from my Life_Max using Tapatalk
Hello owners of Samsung Galaxy Tab S 10.5 WiFi (chagallwifi) SM-800,
Let's save some more devices from the garbage. Here is a build for LineageOS 17.1 for SM-T800 (tested only on this device).
Tested and working so far
Wifi.
Camera (front and back).
Location.
Touchscreen.
All other sensors.
I am not aware of anything broken.
This is a plain build of LineageOS 17.1, with only minimal SELinux policy modifications to make the device work.
If you prefer to use OpenGApps, download signed-ota_update-plain.zip, if you care more about privacy and prefer a degoogled version, download signed-ota_update-microg.zip which has microG bundled in it.
Special thanks to owners of:
LineageOS: https://github.com/LineageOS
Exynos5420: https://github.com/exynos5420
Kernel source.
microG: https://github.com/microg
Guide to building LineageOS with microG: https://gist.github.com/dic1911/407184ee427c50ad0066af643a20254f
microG Mobile Services: https://github.com/lineageos4microg/android_vendor_partner_gms
You are welcome
Great news, thanks!
Could you please clarify what you wrote about SELinux? Is it active and enforcing? Is encryption supported?
porcino said:
Great news, thanks!
Could you please clarify what you wrote about SELinux? Is it active and enforcing? Is encryption supported?
Click to expand...
Click to collapse
SELinux is active and enforcing, the modifications are because the default SELinux policies in LineageOS contradict with those of the device (probably because the device ones are few years old). The modifications are to remove some strict policies that would break device drivers like the camera and sensors if left enabled.
Encryption is disabled.
minashokry said:
SELinux is active and enforcing, the modifications are because the default SELinux policies in LineageOS contradict with those of the device (probably because the device ones are few years old). The modifications are to remove some strict policies that would break device drivers like the camera and sensors if left enabled.
Encryption is disabled.
Click to expand...
Click to collapse
It's great that SELinux is on, and it is expected to have minor cuts in the policies. They are a pain to develop. It has to be a separate project...
What's going on with encryption? Forgive me for a silly question, I just see this feature missing in LOS17 ROMs for other devices as well... Is it something LOS specific?
porcino said:
It's great that SELinux is on, and it is expected to have minor cuts in the policies. They are a pain to develop. It has to be a separate project...
What's going on with encryption? Forgive me for a silly question, I just see this feature missing in LOS17 ROMs for other devices as well... Is it something LOS specific?
Click to expand...
Click to collapse
Honestly I don't know about encryption. I didn't care about it while building this image.
minashokry said:
Honestly I don't know about encryption. I didn't care about it while building this image.
Click to expand...
Click to collapse
Fair point - it has to be running at all before looking at the advanced features. For the first release it's quite a remarkable result. It would be nice to have encryption on the to do list...
Another silly question: the speakers of this tablet are not very loud. Is it difficult/possible to boost their volume a little?
Will test this out. I had flashed LOS17.1 by @8224Freak, but its SELinux is disabled. Will see if this one works same or better. Does this build contains the most recent security patch?
@minashokry thanks for the build. Camera only works with picture taking. It freezes when video recording is ended.
@minashokry I have been using your build on my T800 and likes it a lot. In addition to the camera video recording freeze, mic does not appear to work well. I tried some audio recordings but only hear tiny sound during playback. I was wondering if you are planning on updating the build once awhile to at least include new security patch., or this is it - no more update? Thanks again for build this smooth LOS17 rom for the old tablet.
foolone said:
@minashokry I have been using your build on my T800 and likes it a lot. In addition to the camera video recording freeze, mic does not appear to work well. I tried some audio recordings but only hear tiny sound during playback. I was wondering if you are planning on updating the build once awhile to at least include new security patch., or this is it - no more update? Thanks again for build this smooth LOS17 rom for the old tablet.
Click to expand...
Click to collapse
Bump
Unfortunately did not get very far using either of these builds (plain or microG). In both cases, I'm unable to read or write to the internal storage on the tablet. File manager does not read any contents of the internal storage, fails to create a directory in internal storage, and can't download/save a file from the internet. The LOS 17.1 by @8224Freak does not have this problem, so assume it's something unique to these builds.
I also found that when I formatted an SD card for use as tablet storage (i.e., as an extension of the internal storage), it insists that the card is not inserted every time I power on the tablet. If I eject and reinsert the card while still powered on (no power cycle) it recognizes it and is okay from there.
Don't know if this is related to the above, but the native camera app insists that I must "Insert an SD card before using the camera" even though an SD card is plainly inserted and recognized by the rest of the system.
minashokry said:
Honestly I don't know about encryption. I didn't care about it while building this image.
Click to expand...
Click to collapse
Hello. I've tested your ROM just out of curiosity -- encryption works! This makes your ROM the leader in security! Well done, thanks!
Apart from this... I found a fault with video rendering. At some resolutions the video renders at a wrong scale, larger than the window or the screen. This happens with different websites. I am using Brave browser, which works fine on the same device with LOS-14.1. The same rendering problem is evident in the other LOS-17.1 ROM as well (by 8224Freak). It might be codec related.
Has anyone found a way of dealing with the video rendering fault in Brave/Chrome/Firefox?
What is the link to download this rom? I can't find it anywhere in this thread.
mmaazzaa said:
What is the link to download this rom? I can't find it anywhere in this thread.
Click to expand...
Click to collapse
Use the attachments to the first post "signed-ota...zip".
Thank you. Due to the file name I mistakenly thought it was just an update for the rom, not the rom itself.
Tried this ROM again (signed-ota_update-plain.zip), different screen resolutions, different screen densities - still video playback issues in browsers including Brave. The fault manifests itself as the video being zoomed in, so that only a part of it remains visible. The playback freezes for a fraction of a second occasionally, producing a "metal" screeching sound while doing it. In general this ROM feels a bit laggy. So, going back to lineage-14.1-20220107-UNOFFICIAL-chagallwifi, which feels cleaner, much faster and similar to this one has SELinux+encryption working.
Before anyone asked, the same video playback issues just without freezing I observed in lineage-17.1-20220504-UNOFFICIAL-chagallwifi, which is under active development now. The latter does not have SELinux+encryption though.
So, for now, the benchmark is set by DarkExistence for this device.
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T800
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com
Just tried this rom, I'm pretty sure the hitching and video playback issues are because the gpu is sitting at 0% utilisation so it's using the cpu for rendering... which would explain things
I downloaded and installed "signed-ota_update-plain.zip". But Google account is not added. There is no Google Play. Thank you to those who will help.
I installed Gapps and OK.
ahmetdamar said:
I downloaded and installed "signed-ota_update-plain.zip". But Google account is not added. There is no Google Play. Thank you to those who will help.
Click to expand...
Click to collapse
Did you install Gapps or its equivalents?