Last Update:
kevdliu said:
Hey everyone,
The hardware condition of my phone has been degenerating at a pretty fast pace. Today it's finally relieved of active duty. So I guess this marks the end of the vivow division of team N7.
However sources will remain open on github and so if any devs want to be added to the members list feel free to pm me.
Thank you guys so much for your support and good luck to aeroevan, team evolution and everyone else for the future development of this wonderful phone.
My time here is up
Over and out
Click to expand...
Click to collapse
SOURCE
Team
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Presents:
CyanogenMod 10 for HTC VivoW
Rom Downloads:
ROM V0.3
Aeroevan's 10.5 kernel not required but strongly recommended
JB Gapps
More info and changelog on second post.
Credits:
- Aeroevan
- Andromadus
-Firetop
-elicik
- ...
Source: Source is HERE
Changelog:
v0.3:
1) Fix camera and flash
2) Fix MMS
3) Fix bootloops and stuck on "Starting Apps" issue
4) Aeroevan's kernel no longer required
v0.2:
1) CM statusbar and lockscreen mods functional (Powerwidget, BatteryMods, Lockscreen Weather etc.)
2) Improved capacitive buttons backlights
3) New OTA app
v0.1: Initial Release
Working:
- Wifi
- Phone & Data
- GPS
- BT
- Audio
- USB Mount
- Sensors
- Camera
- MSM
Not Working:
- Camcorder
- FFC
Team
Presents:
CyanogenMod 10 for Galaxy Nexus
No ROM yet. But since I made it public that i will no longer be working with Team N7 on the Incredible 2. I will keep working for the Team on Gnexus ROMs. Stay toned!
P.S I do appologize for my lack of help to Incredible 2 ROM. I Helped for as long as i could. Now time to move on to new devices. Everyone in this thread is awesome!
Credits:
- Aeroevan
- kevdliu
- Andromadus
-Firetop
-elicik
Sweet. I may get in on this.
Sent from my Incredible 2 using Tapatalk 2
Great work! Syncing right now
Thanks dude. I'll grab this tonight and start working towards some fixes.
Let me know if theirs anything I could try to input ukk
follow me on twitter @pprice520
Desire S and Desire HD now has working audio. It has to do with the name of the driver from what I read.
Sent from my Incredible 2 using Tapatalk 2
72ls1 said:
Desire S and Desire HD now has working audio. It has to do with the name of the driver from what I read.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
I found this https://github.com/Andromadus/android_device_htc_msm7x30-common/commits/jb
kevdliu said:
I found this https://github.com/Andromadus/android_device_htc_msm7x30-common/commits/jb
Click to expand...
Click to collapse
I wonder if going from ICS to JB will prove as problematic for the Dinc2 as going from GB to ICS. It would seem that it shouldn't be as difficult, but I"m wondering if something like Project Butter will require all new drivers again. Here it is like 8 months after ICS release and still has a massive amount of issues on our device (so much so CM team won't do nightlies yet).
ph1nn said:
I wonder if going from ICS to JB will prove as problematic for the Dinc2 as going from GB to ICS. It would seem that it shouldn't be as difficult, but I"m wondering if something like Project Butter will require all new drivers again. Here it is like 8 months after ICS release and still has a massive amount of issues on our device (so much so CM team won't do nightlies yet).
Click to expand...
Click to collapse
Yeah I was checking the Inc forum since I had one and there jb is further along then ours. Ouch we will get there
Sent from my Incredible 2 using Tapatalk 2
72ls1 said:
Yeah I was checking the Inc forum since I had one and there jb is further along then ours. Ouch we will get there
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
Not to worry chaps. Our top men are on the case.
At first I thought, where is the ROM... Then I realized I misread and it is only the source! @[email protected] Ooooh... It is times like this, I wish I knew more about coding for Android. I have NO idea what to do after I download source code of any android OS. Are there any tutorials to tell you how to start messing with the code (properly, and not just randomly)?
litetaker said:
Not to worry chaps. Our top men are on the case.
At first I thought, where is the ROM... Then I realized I misread and it is only the source! @[email protected] Ooooh... It is times like this, I wish I knew more about coding for Android. I have NO idea what to do after I download source code of any android OS. Are there any tutorials to tell you how to start messing with the code (properly, and not just randomly)?
Click to expand...
Click to collapse
+1 for a tutorial
Unfortunately a tutorial wouldn't do much good considering you'll want to know, at least, Java, C++, Python, bash, and a fair amount of linux to really grasp what is happening in the code. Maybe a place to begin is learning and understanding each of what I've listed.
nukified said:
Unfortunately a tutorial wouldn't do much good considering you'll want to know, at least, Java, C++, Python, bash, and a fair amount of linux to really grasp what is happening in the code. Maybe a place to begin is learning and understanding each of what I've listed.
Click to expand...
Click to collapse
by in large yes, although many *well known* aosp *devs* are really just guys who scour github for fixes on similar devices or by others for the same device
so if thats the end goal (and for many im sure it is), just learning how to set a build environment and a few basic terminal commands will get ya going
Good point. I couldn't imagine taking on a task of attempting to rebuild something without knowing the language, but I've been coding half of my life now and met a lot of the repercussions of doing so. I'm not great at writing guides but if someone was to begin one, I wouldn't mind throwing in my input where it could help.
nukified said:
Unfortunately a tutorial wouldn't do much good considering you'll want to know, at least, Java, C++, Python, bash, and a fair amount of linux to really grasp what is happening in the code. Maybe a place to begin is learning and understanding each of what I've listed.
Click to expand...
Click to collapse
nitsuj17 said:
by in large yes, although many *well known* aosp *devs* are really just guys who scour github for fixes on similar devices or by others for the same device
so if thats the end goal (and for many im sure it is), just learning how to set a build environment and a few basic terminal commands will get ya going
Click to expand...
Click to collapse
Well, I do have some knowledge on Java, a lot less on C++. Obviously, I knew that there are prerequisites to this; I don't expect to open a book and become an instant Android dev sensation! But, even with my (admittedly simple) knowledge of Java and C++, I have NO clue how to get things going. So, this is what I meant with the tutorial. It is very daunting to work on a project that has such a HUGE source code... I've been working on programs with a maximum number of files in 10s... Sooo.. I'd like to know what helped kick your android programming in the right direction and, hopefully, start my own way into this world! I wanna be a contributor, man! Not just a leech!!!
litetaker said:
Well, I do have some knowledge on Java, a lot less on C++. Obviously, I knew that there are prerequisites to this; I don't expect to open a book and become an instant Android dev sensation! But, even with my (admittedly simple) knowledge of Java and C++, I have NO clue how to get things going. So, this is what I meant with the tutorial. It is very daunting to work on a project that has such a HUGE source code... I've been working on programs with a maximum number of files in 10s... Sooo.. I'd like to know what helped kick your android programming in the right direction and, hopefully, start my own way into this world! I wanna be a contributor, man! Not just a leech!!!
Click to expand...
Click to collapse
You can start with this:
http://forum.xda-developers.com/showthread.php?t=1762641
Just replace where it says:
dastin1015 said:
6) Initialize the repo:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1
Click to expand...
Click to collapse
Replace "repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1" With our repo. Use "repo init -u git://github.com/VivowJB/android.git -b jellybean"
Then you can start to sync and compiling from what we have
---------- Post added at 02:58 PM ---------- Previous post was at 02:47 PM ----------
nitsuj17 said:
by in large yes, although many *well known* aosp *devs* are really just guys who scour github for fixes on similar devices or by others for the same device
so if thats the end goal (and for many im sure it is), just learning how to set a build environment and a few basic terminal commands will get ya going
Click to expand...
Click to collapse
Also that is basically exactly what i do. I would never consider myself a real developer. I'm just very good at merging things. I look at github repos to find anything i can that might help me fix what im looking for.
An exmaple of that is im looking for things like this: https://github.com/fat-tire/android_device_bn_encore/commit/3d7dd5c8f124668b754821d0361fab1694e5dfda
or things like kevin found. They give me a baseline of what needs to be done to fix it. I also contact known developers that have a fix for it (No matter what device they are on) Because i may not know C++ but i just need to know the break down of what was done. I know Java. And i know how to set a build environment and know the terminal commands for linux. (Ubuntu and CentOs).
I contacted devs like fattire which has a ROM with working audio. And i get them to give me the details on what was done. I look at their github and use that as much as possible. Then i learn that fattire is using only the legacy sound stuff. No audio_policy.conf. And a qualcomm device will be different. So i contact jcsullins for info on audio on the HP Touchpad (Which is a qualcomm device).
Once i have enough details and info i start my own patchs and fixes. I merge some stuff with what they have, and the info they gave me (the devs and githubs) to make something working for our phones.
and anyone can start do that. And we hope you DO start to do it because anyone keeping knowledge to themselves is no help and well.. just a waste. This is a community thing and we hope to get it working as fast as possible.
Which reminds me. Kevin. You know i was talking about a possible fix for audio last night? Seems like ill be testing a few builds tonight with some fixes ive done. Ill let you know on Gtalk.
+1 fattire
He has done a great job getting the community to step it up on the Nook Color. When ICS/CM9 came out, instead of posting ROMs he put up a how to build thread, it was/is amazing how many people started to build there on.
https://androidgroup.googlecode.com/files/Introduction to Android.pdf This may help if you decide to dive into developing more in-depth. It's really only a summary of the architecture, but I think it's a good one that breaks up what is happening. It's dated but most of it is relevant. Knowing the architecture is great importance in a project with this much code.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AndroidInsomnia Presents:
the OFFICIAL MIUIAndroid 2.3.9
The best MIUI English translation around, it's the MIUIAndroid.com build. This is THE Official Releases for MIUIAndroid. I put in a lot of time to getting this build to this point so I do hope you enjoy them.
Please remember that MIUI is created in China and is controlled by Xaiomi
I will be providing support EVERYWHERE! However, official support is provided at MIUIAndroid or MIUI.us
New releases planned for every Friday
This is an excellent ROM. It introduces the first non-CyanogenMod/carrier/manufacturer framework overhaul of Android 2.3.7 and it's EPIC!
Recommended Install Instructions
1. Wipe Data/Factory Reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
IF YOU ENCOUNTER PROBLEMS, REINSTALL USING THE ABOVE AND AFTER BACKING UP YOUR SD CARD ADD:
5. Format /sdcard
The Kernel is provided by Cayniarb at Tiamat-dev.com What an excellent kernel! Thanks!
MIUIAndroid
Download from MIUIAndroid.com: http://files.miuiandroid.com/2.3.9/miuiandroid_Glacier-2.3.9.zip
Download from AndroidInsomnia: http://www.androidinsomnia.com/MIUIAndroid/miuiandroid_Glacier-2.3.9.zip
Download from AndroidFileHost: http://www.androidfilehost.com/main/HTC_Glacier_Developers/jhutson456/MIUI/Official_MIUIAndroid/
Download from Goo-inside.me: http://goo-inside.me/devs/miuiandroid
md5sum: ff97592dd04e219c45d3f5035edfa729
You can also get MIUIAndroid on Rom Manager!
Change Log:
This is ported using the Official translation from MIUIAndroid of the Desire HD and the newest CyanogenMod Glacier build compiled by me as the HTC Glacier base.
Code:
Full Change Log:
NOTE: No longer uses the CM7 Nightly for the Glacier base. I'm using a compiled version I did. :-)
BONUS:
WIFI Calling - Now bundled in (thanks jimbo11883 for the troubleshooting good work)
Haptic Feedback on Stock Keyboard Works - miui.us fix
Multi-Boot - /system/framework/andrpod.policy.jar hack
Trackpad Wake - /system/app/Settings.apk smali hack
Fixed Tiny MMS - /system/app/mms.apk from desire z
Replaced Gallery -/system/app/gallery.apk (some were complaining of small gallery)
Edited the /system/etc/APNs - from cm7
Edited the /system/etc/gps.conf for faster GPS lock - from cm7
Edited the files in /system/etc/*.csv to fix the dysfunctional headset microphone!
Edited the build.prop to hopefully increase stability, speed, and smoothness.
[Lock screen, Status bar and notifications]
Fix in some cases, the status bar doesn't display the operator name
[Desktop]
Optimisation to modify the default system wallpaper
Code:
[b]NOTES:[/b]
ISSUES? Logcat them! [url]http://forum.xda-developers.com/showthread.php?t=1378491[/url]
-Known Issues:
1. To get muli-boot menu to work on both builds you have to toggle the
/menu/System/Button Settings/Disable on Lockscreen
switch on then off again.
-Superuser is off by default. To fix this:
1. Open the Superuser App
2. Press your 'Menu' key
3. Select Settings
4. Turn 'Root Permission' ON
5. Enjoy sticking it to THE MAN!
-The Time Zone is set by default to China. To fix this:
1. Press your 'Menu' key
2. Press 'Settings'
3. Select the 'System' tab at the top
4. Scroll down to 'System and Hardware' and press 'Date & Time Settings'
5. Press 'Select Time Zone' and choose your correct Time Zone
6. Enjoy
-Trackpad Wake:
1. Press your 'Menu' key
2. Press 'Settings'
3. Select the 'System' tab at the top
4. Scroll down and click on 'Button'
5. Toggle 'Trackball Wake'
6. Enjoy
-Enable Apps to request Superuser Permissions
1. Open the Superuser app
2. Press 'Settings'
3. Toggle "ROOT permission"
4. Enjoy
- _________ Theme element doesn't seem to work after installation.
1. Reboot your phone. Fixed?
2. Reboot into recovery and clear caches and fix permissions. Fixed?
3. If it's not fixed at this point, imediatly go into theme manager
and re-install the theme.
- My GPS isn't working.
1. Download (or open if installed) "GPS Status and Toolbox" by EclipSim.
2. Open it.
3. Press the 'Menu' hard key
4. Select 'Tools'
5. Select 'Manage A-GPS state'
6. Select 'Reset'
7. Reboot your phone AS SOON AS IT'S DONE.
8. Enjoy!
This ROM brought to you by JHutson456
I would like to take a moment to thank TrueBlue_Drew, Tiger013, MIUIAndroid, CyanogenMod, Tiamat, Vaelek, Kidromulous, Virus and the whole InfectedROM Crew, and everyone who helped me get here! I'd like to mention ckisgen, Rafy, TDJ, xboarder56 and anyone I forgot to mention before. We all learn off those who came before us. I hope I can contribute in a positive way before I finish I'd like to add a thanks to SuperKid, MarkHUK, cayniarb, leeech, linds6630, and blind. I've been able to grow a lot as a dev due to the people mentinoed above and below. It really needs to be said, "nani gigantum humeris insidentes" We are dwarves standing on the shoulders of giants.
I couldn't have finished this without minus21. Thank you. Another thank you is due to boardopboy for flashing different variants at the drop of a hat we blindly lead and he blindly follows .
The Team That Brings You All The Latest and Greatest Roms: AndroidInsomnia
You can now join our new irc channel and talk directly with us. This is new but we hope to have it fully established soon. It is live now
irc.irondust.net
#AndroidInsomnia
[url]http://webchat.irondust.net/?channels=AndroidInsomnia
Join us today
You can check out CyanogenMod's entire source including the Kernel for this at CyanogenMod's GitHub
Tiamat's source for the kernel can be found HERE
Devs:
TrueBlue_Drew
JHutson456
Cnote74
iblaststatic2020
Blackwing182
Option94
Graphics and Themes:
Tiger013
JunkDrugler
Testers:
boardopboy - Testing Lead
tw39515
minus21
altroy
Flynn2
nicgraner
Elloco305
You can follow my Twitter HERE
You can follow my Google+ HERE
You can follow my Facebook HERE
Looks good will test out im currently running sense 3.5 by thedereck his but I love miui. Thanks bro
This didn't get to much play for a Saturday, It's probably all of the fans of MIUI that already have some one here porting it over.
Good Luck.
As this was my first build ever I had it being tested by our team all day Friday and got it live here Saturday kinda late. It's going to be updated no later than Friday nights if it can be helped however. Possibly faster depending on work (sometimes I work night shift sometimes day shift) but this is a high maintenance ROM and I'm well aware of it. Being new, I just didn't want to release it early (I had it ready around 9am pacific) only to find out I'd missed something simple in the process, that would have been silly.
Just so you know there is already a supported miui thread for our device made by thederekjay who is supported by miui.us and my friend he is a beast he makes his own kernels for miui releases every Friday which have amazing speed and crazy battery life
So just a heads up if your looking to be a miui dev you got a lot of work to do
Sent from my HTC Glacier using xda premium
Well yeah but lets give his team some credit for putting the effort into getting this ready. Thanks guys, I'll see if I flash it today
Sent from my HTC Glacier using XDA App
Laazyboy said:
Well yeah but lets give his team some credit for putting the effort into getting this ready. Thanks guys, I'll see if I flash it today
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Very true but I was just letting him know he has some big competition
Sent from my HTC Glacier using xda premium
Its no competition, I don't know about kernels and this is my first ROM for release. Also, he gets his from miui.us and I get mine from MIUIAndroid so... two different starting points. I hope he is successful in his aims as I hope I'm successful in mine. My aim is to create ROMs I enjoy for everyone to use if they wish.
Its based off nightly 205, so is it 2.3.7? And, what sets this apart from tdj's port? Im not troll, just want to hear it from you. You seem to be only one that has flashed it. Is it having the same widget issues as tdj's?
lanternslight456 said:
Its no competition, I don't know about kernels and this is my first ROM for release. Also, he gets his from miui.us and I get mine from MIUIAndroid so... two different starting points. I hope he is successful in his aims as I hope I'm successful in mine. My aim is to create ROMs I enjoy for everyone to use if they wish.
Click to expand...
Click to collapse
That's good we like New devs
I was just informing you that he has a Rom out too and a lot of followers
Please don't think I was trying to bash you bc im not I was just letting you know
Sent from my HTC Glacier using xda premium
The base comes from China, there's only one place both get it from, you can look through the original release and tell they're exactly the same. Either way good luck with your end of it as it all depends on two factors, how well you port it and how good the base is prior to you getting it.
Orical said:
The base comes from China, there's only one place both get it from, you can look through the original release and tell they're exactly the same. Either way good luck with your end of it as it all depends on two factors, how well you port it and how good the base is prior to you getting it.
Click to expand...
Click to collapse
+1
Sent from my HTC Glacier using xda premium
Orical said:
The base comes from China, there's only one place both get it from, you can look through the original release and tell they're exactly the same. Either way good luck with your end of it as it all depends on two factors, how well you port it and how good the base is prior to you getting it.
Click to expand...
Click to collapse
Though you are correct that they come from the same Chinese build, MIUIAndroid and miui.us do differ in minor ways. I'm fairly new to MIUI myself and haven't used the miui.us build other than briefly. I am going to be exploring these differences over time. Honestly, a major portion of the reason I chose MIUIAndroid's version of the port is because I know Option94 was the main guy at miui.us on the glacier before he changed to an iPhone and Derek asked if he could take over. I wanted to leave that alone and do it different.
lanternslight456 said:
Though you are correct that they come from the same Chinese build, MIUIAndroid and miui.us do differ in minor ways. I'm fairly new to MIUI myself and haven't used the miui.us build other than briefly. I am going to be exploring these differences over time. Honestly, a major portion of the reason I chose MIUIAndroid's version of the port is because I know Option94 was the main guy at miui.us on the glacier before he changed to an iPhone and Derek asked if he could take over. I wanted to leave that alone and do it different.
Click to expand...
Click to collapse
Well I'm glad that you feel up to the project and hopefully you learn from it, most of the roms out are based off of official builds direct from HTC or other and true development exists from scratch so it's kind of interesting that anyone considers them selves a "developer" so to say when modifying or porting over an official base to another device, it's a good starting point in understanding how everything works and taking on the challenge of using your spare time and time away from private responsibilities of work and family to better educate your self on something that will benefit you and others somewhere down the road.
Orical said:
The base comes from China, there's only one place both get it from, you can look through the original release and tell they're exactly the same. Either way good luck with your end of it as it all depends on two factors, how well you port it and how good the base is prior to you getting it.
Click to expand...
Click to collapse
the truth is you are correct, but at the same time you are incorrect... now the main difference is in the strings. "strings" are what is changed for language. for example all the text you read and see are referenced to the strings. when you decompile and .apk there is a file within called strings.xml located in /res/values/ for english you would create /res/values-en/ the -en denotes english.. so on so forth... so although they come from the same place_MIUI China) there is a much different process in the preparation of each rom. MIUI.us uses a buildbot created by the team thats on their server to do the port and inject all correct strings... I have also wrote a buildbot script wich is very detailed and automates the entire process so i can get the entire thing done in about 5min uploaded with out having to do anything... The truth is that i welcome all new dev, but there are few things that you will need some coding experience to fix... good luck on your port...
I don't know anyone that lasts very long in android if they look at it or do it for competition, that's where trouble starts. most do it to learn, as a hobby, for fun and to help others. you don't get into android to compete, that's where a lot of things turned south. we are not and never will be here to compete and hopefully no one will take it that way. we get to learning and make a lot friends and meet really good people witch really makes android what it is. I only hope others can let go of personal grudges and take a wider veiw of why most devs and themers do what they do. and let the past be the past. we are here to create not destroy. to learn not deter, and to help and share as others have done with us to get us where we are today. any way I hope we can all move past any animosity and and get back to the real reasons anyone comes to android.
I rooted my nephew phone today n ran this Rom on it for him I myself played with it a little before heading back to tdj 3.5 so far no issues to report your Rom is smooth n my nephew can't put his phone down lol thanks bro
Another MIUI ROM going to give it a shot
Since lanternslight wont answer, let us know if the Widgets on the home screen update. Thnx
BeEazy10 said:
Another MIUI ROM going to give it a shot
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
I am lanternslight dude, lol. I was just busy with my 13.5 hour work day plus wife and two kids Honestly after last night I'm tired lol. But, I don't use Widgets, so I'll set one right now, and check it in a few hours when I wake up. I'll let you know. I've only been in Derek's thread once or twice so I don't know what the story here is. Can you give me some details please?
Thanks to those positive comments, you guys rock!
Edit: hahahahaha that's funny, I thought I was in rootzwiki. This why it's better to keep everything localized at ACS so far as q&a and support type stuff goes, I use forum runner to keep plates spinning while I'm not at the computer (this is 95% done mobile hahaha. Anyhow, I'll post the results at ACS in the am. Goodnight guys and thanks for the feedback!
Edit 2: I have Plume, the clock, and setcpu set as widgets. Clock keeps good time and setcpu updates every 5 seconds, like I've set it to. Plume I'm not sure of.
Wanted to update you one last tome, I hate keeping you guys waiting.
@the person asking about Android version. Desire HD build was 2.3.5, CM7 build was 2.3.7. Build prop for this is 2.3.5 but I set that... I've been trying to get a good answer on how to no BS answer the question, but have been mobile on 2g all day. Best answer ATM is that this is 2.3.5. But I'm no 100% there. I'll let you know soonish.
Hello XDA and welcome to your Christmas present from me! Jelly Mod is basically Nevergone's 4.3 build from CM source with various added tweaks from myself. Before I start, I would just like to give major props to: Cyanogen Mod, Google, HTC, Flinny, Flemmard, guest1, mosi110, kylon, szezso, nadlabak and NeverGone\RU. Without them our device would suck, literally. Also before anyone asks, KitKat is in the pipeline! Please post any comments, bad links or improvements. This will help make the ROM better. Thanks for downloading, don't forget to hit thanks!:good:
Bugs:
GEL "Ok Google" not working;
Data usage calculation bug; (probably never going to be fixed:crying
You tell me!
Features:
Based on CM 10.1;
Android 4.3.1;
Blazing fast!!
Latest Gapps;
Various battery percentage in status bar options;
Choice between GEL and Trebuchet;
Newer Trebuchet, with live folders, icon pack support and other stuff;
Supported on the G2 and Desire Z;
Hosts tweaks, no ads!
Build prop tweaks;
Advanced reboot;
T9 dialer;
Camera button options (wake/unlock/peek/playback control);
All device hardware fully functional, including wifi, bluetooth, camera, camcorder, etc;
Bloatware and unnecessary applications removed;
Rooted, deodexed and slim!
All apks zipaligned on boot (makes apps load faster);
Faster internet and battery tweaks;
Better jpg image quality;
Better camera recording quality;
Smoother video streaming;
Faster wifi connect/disconnect;
Overall smoothness improvements;
See for yourself! Browse through settings and find something to your liking!
Version 1.0.0:
CM source.
Install:
Coming from another ROM?
-Wipe data, wipe cache, wipe dalvik cache, install ROM, install Gapps and let it settle for a few minutes.
Just an update?
-Wipe cache and dalvik cache, install new version of ROM. Any problems? Follow "Coming from another ROM?" steps.
Download:
https://sites.google.com/site/masterleron/
Sources:
Thanks to NeverGone\RU:
Local manifests: https://github.com/NeverGone-RU/Andromadus
Device tree: https://github.com/Andromadus/android_device_htc_vision
MSM7x30 common: https://github.com/Andromadus/androi...msm7x30-common
Kernel: https://github.com/Andromadus/htc7x3...andromadus_4.3
Reserved...
Sent from my Nexus 7 using Tapatalk 4
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gonna try soon!! Thanks a lot!
Sent from my HTC Desire Z using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?
HTCDreamOn said:
http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?
Click to expand...
Click to collapse
Remember Jelly Baby, it has all of those tweaks plus some more as its 4.3.1 I would try both, but this is definitely blazing! BTW it's not just build prop tweaks, I spent a LOT of time on this. I wouldn't release a new ROM just for build prop tweaks, and judging by that thread, most of which are just placebo anyway.
Sent from my HTC Vision using Tapatalk
wow, nice job. I'll try it for sure.
HTCDreamOn said:
http://forum.xda-developers.com/showthread.php?t=2544330
Also what does this have over NeverGone's 4.3 which has been running great for me for weeks on end?
Click to expand...
Click to collapse
*cough*...
I'm not saying it's that terrible, though. Maybe someone will want to use my build shipped with GEL and with mobile data fixed out of box.
NeverGone\RU said:
*cough*...
I'm not saying it's that terrible, though. Maybe someone will want to use my build shipped with GEL and with mobile data fixed out of box.
Click to expand...
Click to collapse
Mine has GEL and mobile data out of the box as well. Those tweaks are proven to work BTW. Oh and mine is faster.
Sent from my Nexus 7 using Tapatalk 4
Thanks to everyone who appreciates my work.
masterleron said:
Mine has GEL and mobile data out of the box as well. Those tweaks are proven to work BTW. Oh and mine is faster.
Click to expand...
Click to collapse
That's exactly what I'm saying -- GEL and mobile data are the only differences in your build.
"Faster" with only media "tweaks" applied to build.prop? Mind sharing how is it possible?
Speaking of "proven to work"...
LaraCraft304 in [URL=http://forum.xda-developers.com/showthread.php?t=2544330]demystifying build.prop[/URL] thread said:
Entries that DO NOT exist in the source:
(Again: I scaveged all Android source code)
...
ro.media.dec.jpeg.memcap
...
All ro.media.enc* entries
A more elegant alternative would be to edit /system/etc/media_profiles.xml
Click to expand...
Click to collapse
These are the only tweaks you applied. It just can't be "faster" in any way possible.
Initially I thought that you finally managed to build Android from source - after all PMs you sent me, you should get at least somewhere!
Honestly, I was disappointed.
Again, it's not bad that you're modifying others' work -- we all started with something small. But then you should at least give a proper description of your work and not claim something that isn't true. Remember, running a diff between two builds will show everything you did, and trying to cheat here won't do anything good.
At the moment, JM is my build with GEL on top of it.
I believe you'll add more features to it. Ad-blocking hosts file, zipalign scripts, maybe some apks removal -- all that is currently missing.
Just be fair, that's the only thing I'm asking you as a developer.
NeverGone\RU said:
That's exactly what I'm saying -- GEL and mobile data are the only differences in your build.
"Faster" with only media "tweaks" applied to build.prop? Mind sharing how is it possible?
Speaking of "proven to work"...
These are the only tweaks you applied. It just can't be "faster" in any way possible.
Initially I thought that you finally managed to build Android from source - after all PMs you sent me, you should get at least somewhere!
Honestly, I was dissappointed.
Again, it's not bad that you're modifying others' work -- we all started with something small. But then you should at least give a proper description of your work and not claim something that isn't true. Remember, running a diff between two builds will show everything you did, and trying to cheat here won't do anything good.
At the moment, JM is my build with GEL on top of it.
I believe you'll add more features to it. Ad-blocking hosts file, zipalign scripts, maybe some apks removal -- all that is currently missing.
Just be fair, that's the only thing I'm asking you as a developer.
Click to expand...
Click to collapse
I haven't claimed anything, how am I cheating, its not hard to add hosts scripts and stuff, I'm still working, this is only the first build. If you don't like it, then why tell me I can build from source and give me tips. Jelly Baby started small like this and look where it is now. I WILL add more tweaks, calm down. Now can we please keep this on topic. Also, I've read various places that those build prop tweaks work, one post in some random thread is not going to change my mind.
Sent from my Nexus 7 using Tapatalk 4
masterleron said:
I haven't claimed anything, how am I cheating, its not hard to add hosts scripts and stuff, I'm still working, this is only the first build. If you don't like it, then why tell me I can build from source and give me tips. Jelly Baby started small like this and look where it is now. I WILL add more tweaks, calm down. Now can we please keep this on topic. Also, I've read various places that those build prop tweaks work, one post in some random thread is not going to change my mind.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you refuse to build from source you're gonna have to do more things than zipkang and chuck in some build.prop tweaks. Also listing features that are already in CyanogenMod such as T9 dialer isn't gonna fool anyone. Of course you've read in various places that those tweaks work, the amount of stupid scripts in the software development and hacking section of XDA is absolutely astounding. However there are multiple people who have been through the actual source code of android and PROVED that the build.prop tweaks do not work (http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/ ; http://forum.xda-developers.com/showthread.php?t=2544330). Note how I say proved: these people haven't made grand claims and fancy signatures, they've observed, tested, and given an objective answer.
Ok you guys stick with your opinions. As long as others are happy I don't mind.
Sent from my HTC Vision using Tapatalk
Q: I grep-ped through the source code and in no place those props are used. Are you milking thanks?
A: STFU Science, as long as people believe it's faster.
Oh, I'm gonna love this.
Based on CM10.2 (like in title) or on CM10.1 (like in op) ?
Sent from my Nexus 5 using Tapatalk
If you have a problem stfu and leave, its based on cm 10.2
Sent from my Nexus 7 using Tapatalk 4
masterleron said:
If you have a problem stfu and leave, its based on cm 10.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
don't worry, maybe you misunderstood me, I only asked because I've seen two different texts between the title and op.
I am mod of another forum and would like to publicize your new rom (and install and test it on my desire z) .. I just wanted to be sure that i've read it right .. no problem
Oh thx, sorry it's just a bit frustrating random people coming on my thread and basically having a go at me. But thanks.
Sent from my Nexus 7 using Tapatalk 4
masterleron said:
Oh thx, sorry it's just a bit frustrating random people coming on my thread and basically having a go at me. But thanks.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Random people? Someone like NeverGone\RU who has been here a lot longer than you deserves a lot more respect.
I told you stating you were 13 was stupid. I tried "your" ROM and it worked pretty well. Hell I actually used it as stable for a couple of months. Now I was going to try this ROM out but first, you have been blantely showed off as a rip/copy. I dont care but that in the XDA community is a NO NO. Later a complete disrespect for someone like NeverGone who has obviously had more time deving that you.
And Im not a fan of things NeverGone has done either, Ive ripped on him too so this isnt me being his fan or a antimasterleron.
I apoligize to myself for actually thinking you were a real dev. Shame, you had potential but you ruined it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Eos! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Bigrushdog - Project lead, Chief Developer [Xoom || Galaxy Nexus || HTC One (M7)] || Nexus 7
RaymanFX - Co-leader, AOSP code maintainer [Xperia S || Nexus 7 (2013) || OPPO N1 || OPPO Find7a]
jrior001 - Jenkins/Gerrit Admin, CAF code maintainer [HTC One X]
anders3408 - Frameworks Developer [OPPO Find5 || OPPO N1]
Roach - Frameworks Developer [Nexus 4 || Nexus 7 (2013) || HTC One (M8)]
Connor Baker [Nexus 4 || HP Touchpad]
Code:
NX 2.0 Gesture Navigation Interface
EOS Weather Engine
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Network Indicator
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Force Navigation Bar on any device
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded.
Team EOS Nightly builds
Wingray, Stingray, and Everest Downloads
G-Apps Package
PA Gapps
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.4.x COMPATIBLE RECOVERY.
Detailed instructions:
Going to EOS4.4.x from a rom < 4.4.x:
Backup everything !
Go to recovery
Make a full wipe / factory reset
format /system
Flash the rom
Flash optional kernel
Flash gapps
Reboot
Updating from EOS 4.4.x #XX to #YY:
You can usually skip the full wipe step.
If ever you encounter an issue make sure you make a full wipe first before reporting though.
These are only for Bigpart enabled devices. IF YOU DON'T HAVE BIGPART SUPPORT DO NOT FLASH!
Many things are broke, including camera and radios on telephony enabled devices. I'm opening a thread here for the purposes of furthering development and discussion. These builds are only for folks that enjoy punishment and can give guidance on what i need to do to get the broke things fixed. The Eos project is now geared towards supporting modern qcom devices. However, we're fairly close to getting some proper Xoom builds.
I personally want to give a HUGE THANKS to @Schischu for carrying on the Xoom battle! I'm really glad Xoom users have been able to enjoy strong, stable 4.4 builds. Also, I want to give another HUGE THANKS to @Schischu for thinking up the Bigpart kernel patch. That is not my work and I just wanna make sure that's clear.
I am using @Schischu 's device trees and @flar2 's kernel for now. Once we can get reasonable stable, I'll bring in Backtrack support and all that fun stuff. Once again, I give huge props and respect to @Schischu for the amazing work he has done.
Also, I give a huge thanks to @shpitz for giving me what has turned out to be a VERY LONG TERM LOAN on his Stringray! If someone want's to take lead on maintaining and developing Xoom for me, please speak up! @shpitz i'm sure wants his Stingray back sooner rather than later.
Contribute
Gerrit Review
Jenkins Build System
Github
Kernel Source
Reserved for something
Come on in guys! I must really be a glutton for punishment these days!
Ok, let's start with the good news. Wifi, bluetooth, and it looks like the sensors all come up. And overall, the build feels stable. I haven't got random reboots or anything like that.
The bad news: camera and radios are broke. And those are usually the hardest to fix. Eos uses CM tele framework, including the new msim support from CAF. I've trolled every team's repo out there and can't see to get camera right. I do believe i'm close though. I've got about 5 or 6 open commits on Eos review pertaining to tegra2 related display stuff, yet they don't seem to work for me here.
Updated 6/22
What's broke, maybe broke, unknown
-- Problems with EGL config causing launcher wallpaper picker fail, as well as numerous user apps including Amazon Store and likely more.
-- Everest just released, waiting on radio reports.
-- Next day or two, stingray_cdma will release, we'll watch this radio as well.
-- That's all i remember, if i missed some derp, let me know and i'll add to list.
Upcoming and to-do list
-- Charge light on/off toggle (I know you guys missed that one ;D)
-- Boatloads of kernel modules!
-- Backtrack support for those who still want to use their Xoom to pwn Facebook passwords at the local Starbucks :angel:
-- Perhaps overclock by default so we get a stronger device experience out the box
Can a different camera be downloaded from play store and work? Or no the base has to be layed...?
kmcrane said:
Can a different camera be downloaded from play store and work? Or no the base has to be layed...?
Click to expand...
Click to collapse
A third party cam MAY work, but I'm not sure. The stingray I'm using has a deactivated Verizon sim card and I think it was being weird with gapps. I couldn't connect to Play Store. The peculiar thing is, I get a Camera fc. If something was borked with HAL i would get a "Could not connect to camera" error. Definitely worth a shot.
I have used banks gapps (minimal) Or PA gapps, and I used micro modular I think. A long as I get play store and I can download what I want I'm happy. I hate deleting tons of stock apps.
Anything for 2012 Nexus 7? I have one of those too, and dual eos would be perfect.
kmcrane said:
I have used banks gapps (minimal) Or PA gapps, and I used micro modular I think. A long as I get play store and I can download what I want I'm happy. I hate deleting tons of stock apps.
Anything for 2012 Nexus 7? I have one of those too, and dual eos would be perfect.
Click to expand...
Click to collapse
Ya, and as it turns out, looks like i'm maintaining that one too. Now, grouper is rock solid. I haven't opened the thread yet, but dig around the teameos downloads and you'll find it.
bigrushdog said:
Ya, and as it turns out, looks like i'm maintaining that one too. Now, grouper is rock solid. I haven't opened the thread yet, but dig around the teameos downloads and you'll find it.
Click to expand...
Click to collapse
Lol i have been digging around Google and anything i could find with EOS, bigrushdog, r. Ru**ing, I've been eos stalking for a few weeks trying to find a little break.
Thanks!
Sent from my VS980 4G using XDA Free mobile app
Awesome work!! Been using a self compiled build for 2 weeks or so and loving it! Great to see this coming out officially even though some things are broken.
Pls don't tell me will have to do full wipe coming from omni rom to EOS 4.4.2
Sent from my Xoom Wifi using Tapatalk
ahmed007 said:
Pls don't tell me will have to do full wipe coming from omni rom to EOS 4.4.2
Sent from my Xoom Wifi using Tapatalk
Click to expand...
Click to collapse
These builds are only for folks that enjoy punishment and can give guidance on what i need to do to get the broke things fixed.
Click to expand...
Click to collapse
Based on your post, you're not a candidate folk!
Will certainly be trying this out! I'm still glad I stuck with my xoom!
kmcrane said:
Lol i have been digging around Google and anything i could find with EOS, bigrushdog, r. Ru**ing, I've been eos stalking for a few weeks trying to find a little break.
Thanks!
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure there's a VS980 floating around somewhere too ;D
matt4321 said:
Awesome work!! Been using a self compiled build for 2 weeks or so and loving it! Great to see this coming out officially even though some things are broken.
Click to expand...
Click to collapse
Glad to hear you got it compiling. I wanted to wait to get a thread open before addressing all that. So, you wanna maintain the Eos builds? :highfive::highfive::highfive:
Well, for those of you who have flashed, perhaps we should start getting an inventory of what we gotta do still? I mentioned before that as it stands now, cam is broke. Thus Torch is broke. Radio is hard to assess because i don't have a activated SIM. Also, how is the Wingray build? Has anyone successfully loaded gapps yet? If so, please post up or link to the gapps.
bigrushdog said:
Glad to hear you got it compiling. I wanted to wait to get a thread open before addressing all that. So, you wanna maintain the Eos builds? :highfive::highfive::highfive:
Click to expand...
Click to collapse
I'm not a developer I'm afraid as much as I'd like to be.
I can always compile, bit of debugging, test experimental fixes. not sure I'd be able to maintain though. I have basic expeience in C#, not CPP though some practices are transferable.
I used BaNkS GApps back with the original EOS because of the limited System partition.
With Big Part CM11, I'm using PA GApps. Their Google Camera add-on is working with Photosphere and such.
Will give EOS Revival a shot when I have a little work downtime
Alrighty, just to report: I am currently using a wingray device. I have just flashed the rom (no problems there), and I have just flashed the gapps from here.
So far everything's fine. I can confirm that the camera is currently not functional. However, time does wonderful things!
I do have a question though: I have noticed that the settings app doesn't sport the tablet-optimized two pane layout from previous versions of android. Is that a feature of the rom or is that a kitkat thing?
Anyways, great work! Thank you so much too all who have contributed to it (and one day I hope I can learn how to contribute myself!)
yosterwp said:
Alrighty, just to report: I am currently using a wingray device. I have just flashed the rom (no problems there), and I have just flashed the gapps from here.
So far everything's fine. I can confirm that the camera is currently not functional. However, time does wonderful things!
I do have a question though: I have noticed that the settings app doesn't sport the tablet-optimized two pane layout from previous versions of android. Is that a feature of the rom or is that a kitkat thing?
Anyways, great work! Thank you so much too all who have contributed to it (and one day I hope I can learn how to contribute myself!)
Click to expand...
Click to collapse
Good deal. Wingray will be the first device fully on deck. I'll link to that gapps in the OP. I also noticed we didn't get dual pane on settings. I'll see what I can do. However, I do suspect the dual pane concept as a whole is going extinct. I could be wrong but it's just a feeling I get. Camera is close. Actually, there's a small possibility it's actually audio killing cam. Not sure just yet.
Thanks for being part of the brave elite!
bigrushdog said:
Good deal. Wingray will be the first device fully on deck. I'll link to that gapps in the OP. I also noticed we didn't get dual pane on settings. I'll see what I can do. However, I do suspect the dual pane concept as a whole is going extinct. I could be wrong but it's just a feeling I get. Camera is close. Actually, there's a small possibility it's actually audio killing cam. Not sure just yet.
Thanks for being part of the brave elite!
Click to expand...
Click to collapse
The Xoom CM11 build has dual pane settings. You could see how it was done there?
Sent from my Xoom Wifi using Tapatalk
I've been stalking the Team EOS Gerrit and constantly refreshing the Xoom Development on here. I did run an unstable version a while ago from the Team EOS download page, and even though it was buggy, I liked it.
I think I'll wait until the camera works to flash back to EOS, though.
I like this ROM, especially the NX 2.0. Is there anyway to make an Xposed Module to add the NX 2.0 to other ROMS?
ApertureAndroid said:
I've been stalking the Team EOS Gerrit and constantly refreshing the Xoom Development on here. I did run an unstable version a while ago from the Team EOS download page, and even though it was buggy, I liked it.
I think I'll wait until the camera works to flash back to EOS, though.
I like this ROM, especially the NX 2.0. Is there anyway to make an Xposed Module to add the NX 2.0 to other ROMS?
Click to expand...
Click to collapse
In theory, xposed can do anything. It would be VERY challenging to do a module for it. Especially when I merge http://review.teameos.org/#/c/142/
bigrushdog said:
I'm pretty sure there's a VS980 floating around somewhere too ;D
Click to expand...
Click to collapse
You weren't kidding! And I found a thread from EvilDobe, Grouper up and running great... Xoom will be in the next couple days.
Sent from my Nexus 7 using XDA Free mobile app
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat, ROM for the ONEPLUS ONE
Contributors
kufikugel, SlimRoms, Tylog
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2014-07-21
Last Updated 2014-07-21
Hey guys,
will do a short introduction here due that we have especially on the One plus one a lot android newcomer. 3 weeks ago we got contacted by One plus if we want to be a recognized ROM for the 1+1. Of course it is a pleasure to support this awesome phone. So they send us the device and we worked on it the last 2 weeks.
Short note to SlimRoms as a whole....we are an AOSP based ROM. We are one of the rare roms which still develop a lot themselves. We have a user base around 1 million ppl. A lot in the custom rom scene already know and used a lot of our features on SlimKat as well on other roms. Even you guys on the CM11S stock firmware are already using 2 slim features (Privacy Guard Manager and forward/reverse lookup on the dialer and some other minor things). As well we use features from CM. Thats open source....we share our work and try to improve the things together. That being said, our main aim (and we are known) is to be as stable as possible. We have a clear vision of how our custom rom should be....and with a lot fun we try to achieve it to make us and a lot other ppl happy. We are always open for new suggestiongs or features....just raise them up and we can discuss them and see what we can do with it. But we are not a rom which kangs simply things from others. We basically want to have original ideas and with the ideas and the feedback of our users we will develop it then. So please do not start to we want to have this and that feature from this and that ROM.
SlimKat is in a lot parts pretty different then CM. Some features we do not have.....other features CM does not have. We have just two different ideas of an custom android OS. Both is good and fantastic....just different And this counts of course for every other original development rom like PA, Omni or AOKP.
Aside the original features mentioned in the first post....we have some other original features nowadays: SlimRecents, SlimPie, Slim heads up, Shake events, Chamber of Secret and a lot lot more.
A small word to myself...I am one of the main developers in SlimRoms and leading the development team we have. I like to have OT in my threads as well serious deep discussons about development (check the SlimKat hammerhead thread on xda....thats for me the perfect thread )
And now a last word to SlimKat
1. Read the above linked FAQ...as I said we are different....and this FAQ answers a lot questions. Especially the question about our lower default DPI (which can be changed of course) or that root is disabled by default.
2. Use and please only use our gapps (to get the google gapps like on stock) with SlimKat. On the website we have stable addons and beta addons (which are always on the bleeding edge). Basically both are stable.....so use the latest beta gapps.
3. Which leads me to the release schedule we do. We have every week a weekly. This are builds from latest source automatically builded. They can contain minor bugs but are known to be as stable as the stable build. Every 4-5 weeks we release a stable build for all supported devices. The difference is that they go to internal testing for some time so that our huge tester crew can give the OK that this build can be called as stable.
4. If you get a bug....please refer to the Bugreport section on the website. There it is exactly explained how to report a bug and how to do a bugreport. We have tools which will help you in this case. After that just report this on one of our official channels. We have a team off ppl who will either help you or recognize it as a bug and will throw it into our internal bug tracker.
5. Of course this device is pretty new.....slims code is in some parts pretty different to CM's....so I needed to adapt and change some stuff on CM's device tree to have it working with our source code. That beeing said the first build may have bugs we did not saw till now. We tested deeply everything and it seems to be all perfect...but that does not mean we know every device specific problem which may exist. Especially due that our tester team for bacon is at the moment not that big. But I hope that can change pretty fast
6. Which leads me to the known bugs: Till now only thing we know is that the mic level is a bit low on BT calls and with speaker phone. Headphones and normal phone mic level is completely ok.
7. Kernel....slim comes on most phones with an own kernel based on the stock kernel. Same here on bacon. Basic stuff I did this week on it. So give it a run and do not flash directly another one
8. And last one.....have fun....hoping for a nice thread here....as I said please always read the stuff on the website...FAQ, install instructions, change log etc etc etc
Thanks for your attention and lets slim up our bacon,
Lars
And third post for actual notes:
1. Currently I recommend Philz recovery. Seems to be the best working at the moment for the bacon
2. Do not forget to read the install instructions
:victory: Glad to see this here. Thanks!
Glad to see slim Kat, the more roms the merrier.
Sent from my One using Tapatalk
I am coming from nexus 5 to opo , my go to rom of choice was slimkat or nexus 5 .
I am so happy you guys are supporting opo as well cant wait for the download link
digweed4me said:
I am coming from nexus 5 to opo , my go to rom of choice was slimkat or nexus 5 .
I am so happy you guys are supporting opo as well cant wait for the download link
Click to expand...
Click to collapse
well say thanks to OnePlus They contacted us :good:
Waiting for the build..
And thanks to the op and opo ^^
Welcome to OPO, slimteam
If I understood correctly, you made and AOSP tree for bacon ???
(Every other rom is CM based so far, since omni removed their -non working- build)
kufikugel said:
well say thanks to OnePlus They contacted us :good:
Click to expand...
Click to collapse
most polished rom on nexus 5 and other devies for sure.
Aosp is better than cm we need aosp roms and kernel
Pinch Me I'm Dreaming . Can't wait for my oneplus one
Sent from my Nexus 5 using XDA Free mobile app
Damn can't wait !
bud77 said:
Welcome to OPO, slimteam
If I understood correctly, you made and AOSP tree for bacon ???
(Every other rom is CM based so far, since omni removed their -non working- build)
Click to expand...
Click to collapse
Well that is not so easy to answer....basically we have 3 parts
The base which is pure aosp and has nothing in common with cm.
Then there are hardware related repos. Due that opo is a qcom device it uses heavily caf based hardware repos (BTW aosp is doing this as well). But for opo we need to have some things which are ahead of current aosp source. Of course all ROMs share more or less the same caf code on this part.
Well and you have the device trees and kernel. Like on every device we try to use what the manufacture gives us. Just this time it is CM. But we are on the above mentioned hardware trees on some parts very different. Good example is the BT stack. We use for "caf" devices a completely other then cm which is more near to the aosp BT stack. Of course I needed to adapt this and changed the device trees accordingly. Other example is msim which we do not support at all. Needed to remove the tights to it and replace eg the location provider with the aosp one....etc etc.
To start to bring up a device tree from ground up would not make any sense....it is just double work and at the end you have the same. On Google devices eg we do not do this as well. We use what we get and then we start to change it for our needs and improve it. When you check SlimROMs github for the opo device trees you see that I changed quiet a lot already. Thing which still needs work is the kernel.
You can see here what is done till now:
https://github.com/SlimRoms/device_oneplus_bacon/commits/kk4.4
https://github.com/SlimRoms/device_oppo_msm8974-common/commits/kk4.4
https://github.com/SlimRoms/device_oppo_common/commits/kk4.4
And kernel which got most changes (4 or 5 pages of commits and fixes)
https://github.com/SlimRoms/kernel_oneplus_msm8974/commits/kk4.4
But yeah we will still work on the device tree and especially kernel. Want to change some things still.
Hope that answered your question
kufikugel said:
Well that is not so easy to answer....basically we have 3 parts
The base which is pure aosp and has nothing in common with cm.
Then there are hardware related repos. Due that opo is a qcom device it uses heavily caf based hardware repos (BTW aosp is doing this as well). But for opo we need to have some things which are ahead of current aosp source. Of course all ROMs share more or less the same caf code on this part.
Well and you have the device trees and kernel. Like on every device we try to use what the manufacture gives us. Just this time it is CM. But we are on the above mentioned hardware trees on some parts very different. Good example is the BT stack. We use for "caf" devices a completely other then cm which is more near to the aosp BT stack. Of course I needed to adapt this and changed the device trees accordingly. To start to bring up a device tree from ground up would not make any sense....it is just double work and at the end you have the same. On Google devices eg we do not do this as well. We use what we get and then we start to change it for our needs and improve it. When you check SlimROMs github for the opo device trees you see that I changed quiet a lot already. Thing which still needs work is the kernel.
You can see here what is done till now:
https://github.com/SlimRoms/device_oneplus_bacon/commits/kk4.4
https://github.com/SlimRoms/device_oppo_msm8974-common/commits/kk4.4
https://github.com/SlimRoms/device_oppo_common/commits/kk4.4
And kernel which got most changes (4 or 5 pages of commits and fixes)
https://github.com/SlimRoms/kernel_oneplus_msm8974/commits/kk4.4
But yeah we will still work on the device tree and especially kernel. Want to change some things still.
Hope that answered your question
Click to expand...
Click to collapse
You answered much more than I hoped
I will check all this in the morning
Thank you
Sent from my One
bud77 said:
You answered much more than I hoped
I will check all this in the morning
Thank you
Sent from my One
Click to expand...
Click to collapse
well I can answer it short.....no we do not track 50%-80% of CM repos like most other roms
BTW what I love most on this device is really the battery life.
Here from last 7h and still 50% left ... but without sim today and permanent wifi (with sim and full use I get 24h uptime and 7h SOT without a problem)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kufikugel said:
BTW what I love most on this device is really the battery life.
Here from last 7h and still 50% left ... but without sim today and permanent wifi (with sim and full use I get 24h uptime and 7h SOT without a problem)
Click to expand...
Click to collapse
Whyyyyyyyyyyyy You people do That... Know, i shall not sleep....
have been a slim User since.. i dont know..
can you please... tell me if some of the exclusive apps Like(audioFX, Gallery and Camera) work on SK?
Please say yes...
dj_suca said:
Whyyyyyyyyyyyy You people do That... Know, i shall not sleep....
have been a slim User since.. i dont know..
can you please... tell me if some of the exclusive apps Like(audioFX, Gallery and Camera) work on SK?
Please say yes...
Click to expand...
Click to collapse
Honestly no idea due that I did not test it.
But the gallery is an app you can get on the play store...so no reason that it should not work.
Camera on opo does not have any real special tights into the framework which the other devices do not use as well....I assume it will work.
And audioFX absolutely no idea.
kufikugel said:
Honestly no idea due that I did not test it.
But the gallery is an app you can get on the play store...so no reason that it should not work.
Camera on opo does not have any real special tights into the framework which the other devices do not use as well....I assume it will work.
And audioFX absolutely no idea.
Click to expand...
Click to collapse
as soon the rom became available i will try it.. and test it... tnks for the hardwork...:good::good::good::good::good::good::good::good:
Oh yeah! at last. Since I received my 1 +1 every day looking to see if it appeared slimkat. And finally here it is. I love you more than my phone Thanks.
---------- Post added at 12:55 AM ---------- Previous post was at 12:49 AM ----------
Are DPI low as always?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
Besides selinux being permissive, you tell me
Note: Custom kernels are NOT supported!
If/When the device becomes officially supported, builds will be here https://paranoidandroid.co/downloads otherwise, check the second post for builds
Changelogs
Keep an eye on our Twitter account, @paranoidaospa , as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.
Instructions & requirements
This device runs under lg vendor, make sure you are coming from latest stock firmware.
Download the latest build
Reboot to recovery
Flash the latest build (Note: No need to flash GApps package separately, we include GApps in our ROM package), also make sure to enable TWRP injection
Reboot (In some cases, you may need to set the correct slot before booting ex. if you flashed while on slot a, switch to slot b then reboot, this isn't an issue on most devices, but after wiping data, the system will attempt to boot to the previous slot which most likely will be empty, resulting in a boot screen loop)
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.
Also be sure to join the Paranoid Android Community on telegram (link above), as this is where you'll get the best support from other community users and devs
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz, ROM for the LG V40
Contributors
sirhc
Source Code: https://github.com/AOSPA
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CAF
Version Information
Status: Testing
Created 2020-05-14
Last Updated 2020-05-14
Hey guys, I'm the framework architect over at the PA team, working on a few Oneplus device, but a buddy of mine gave me this one brand new, so i decided to add some PA love for it. Haven't worked on LG devices in years so bare with me please lol. I've started conversion of the trees provided below to be used on CAFs infrastructure (hals, blobs, etc.) But the trees are based on @SGCMarkus work so huge thanks to him for getting development going. The goal is to get this enforcing and fully operational with CAF blobs etc. to improve performance and reliability. These are all unofficial builds and the team is still determining official support, this is based off of enforcing selinux and performance results
Device tree: https://github.com/Sirhc95/android_device_lge_judypn and https://github.com/Sirhc95/android_device_lge_sdm845-common
Vendor: https://github.com/Sirhc95/proprietary_vendor_lge
Kernel: https://github.com/Sirhc95/android_kernel_lge_sdm845
Builds
May 5th - Quartz 3
Be sure to format data if coming from another rom and remember, no need to flash gapps since we bundle them!
Glad to see more people here making ROMs
Yeah, never touched selinux (wanted to fix other issues first), and atm other stuff going on. If you have questions or anything, just hit me up on Telegram (im more responsive there than here) ^^
I built PA for the V50 not too long ago (just to check if a bug was source or device tree related), and i noticed you guys have a ton of common caf blobs there. The RIL Stack very likely wont work on LG devices (LG modified the modem, to the point the CAF stuff very likely cant talk to it... atleast the IMS part, idk about the rest). Just wanting to give you a heads up ^^
Tried that once on the V30, IMS services started, but calling/sms didnt work anymore (it stayed on LTE, but yeah, nothing happened during the call), logs indicated that it cant properly talk to the modem.
Somewhat working on reversing/wrapping the LG Ims implementation though, idk if that will ever work tough...
SGCMarkus said:
Glad to see more people here making ROMs
Yeah, never touched selinux (wanted to fix other issues first), and atm other stuff going on. If you have questions or anything, just hit me up on Telegram (im more responsive there than here) ^^
I built PA for the V50 not too long ago (just to check if a bug was source or device tree related), and i noticed you guys have a ton of common caf blobs there. The RIL Stack very likely wont work on LG devices (LG modified the modem, to the point the CAF stuff very likely cant talk to it... atleast the IMS part, idk about the rest). Just wanting to give you a heads up ^^
Tried that once on the V30, IMS services started, but calling/sms didnt work anymore (it stayed on LTE, but yeah, nothing happened during the call), logs indicated that it cant properly talk to the modem.
Somewhat working on reversing/wrapping the LG Ims implementation though, idk if that will ever work tough...
Click to expand...
Click to collapse
Great to know, I'm more so focused on getting it enforcing (if possible) before I continue, doesn't seem to be working, stays in permissive no matter what I do lol so far basic qti components we provide work, gonna update perf stack from caf to start, guess I can avoid ril for now
Glad to see more ROMs and devs on this. Will be trying this soon.
Would it be possible to make a build without GApps built in, I had planned to use MicroG. Thanks
Any luck with the Modem/Phone issue? I couldnt get it to work on my Sprint version. Thank you.
Hey, amazing rom. Just wanted to start with a positive But no matter what I do I can't get Bluetooth audio to function properly. It connects and I can choose a device, but no matter what, no audio. I've tried deleting all devices, I've actually reinstalled the rom, I've reset the audio device and no matter what, nothing. Also there are some quirks with audio volume overall. Sometimes it won't turn down the volume at all. It's really weird.
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
sirhc said:
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
Click to expand...
Click to collapse
Was going to install it but I'll wait until the next build
sirhc said:
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
Click to expand...
Click to collapse
Just out of curiosity, would there be a possibility of the quad dac functionality being included?
When is the update coming? I'm having the Bluetooth issues as well as my face is causing things to happen on screen during calls even though the screen is off. So the proximity sensor seems to be working but the screen is still detecting touch. Odd..... Looking forward to the update!
Gurnzty said:
When is the update coming? I'm having the Bluetooth issues as well as my face is causing things to happen on screen during calls even though the screen is off. So the proximity sensor seems to be working but the screen is still detecting touch. Odd..... Looking forward to the update!
Click to expand...
Click to collapse
Don't ask for a eta, he's doing this on his spare time. Maintaining multiple devices. For free. In the meantime try to take logs using catlog. Reproduce the issues and save the logs to share.
R800x_user said:
Don't ask for a eta, he's doing this on his spare time. Maintaining multiple devices. For free. In the meantime try to take logs using catlog. Reproduce the issues and save the logs to share.
Click to expand...
Click to collapse
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Gurnzty said:
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Click to expand...
Click to collapse
Ehhh...still frowned upon to ask for eta....
I have this on my V40, anyone have any luck getting Magisk installed on it? I don't know if there is an anroid 10 magisk released for the v40 yet though.
NoburtM said:
I have this on my V40, anyone have any luck getting Magisk installed on it? I don't know if there is an anroid 10 magisk released for the v40 yet though.
Click to expand...
Click to collapse
All recent magisk versions support android 10
Gurnzty said:
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Click to expand...
Click to collapse
Should've mentioned that it's a xda rule. Will take that into consideration thanks. But if you can capture a log. I'm currently not running this ROM to help the cause.
Ainz_Ooal_Gown said:
Ehhh...still frowned upon to ask for eta....
Click to expand...
Click to collapse
Ainz what is your APN settings for this? I can't connect my Sprint phones LTE.
Thank you
Droidman61 said:
Ainz what is your APN settings for this? I can't connect my Sprint phones LTE.
Thank you
Click to expand...
Click to collapse
The same one I always use but idk if my data works on this rom since I still owe Sprint a good amount of money