Well cyanogen 7.2 is out.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
This is primarily for myself. I want to learn how to rom
Angelus359 said:
Well cyanogen 7.2 is out.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
Click to expand...
Click to collapse
That sounds nice and all but this is more of a question which should be in Q&A.
Sometimes the lines between Q&A, and Development blurr... I really wasn't sure which to put it in
I'll make a post there instead.
http://forum.xda-developers.com/showthread.php?t=1534680
this is something to look at. jamie did great work to be honest it deserves the 1.0 but i think he has been rather busy working on different projects (and im sure life )
another thing to think about is incorporating mason's aosp kernel it comes with some more gov's for ppl to play with i have used it on multiple gb aosp roms and it kicks tiamat up a notch
another thread is 7.2 http://forum.xda-developers.com/showthread.php?t=1475989&page=89 i hate to say that these are abandoned but the way ics is working out it gets hard to come back.
just some things to ponder. been messing around with gb aosp to teach myself things here and there so good luck i wish i had more time to keep it going
If you want to stock it down, just build from source. Then add all the good stuff.
Hey y'all,
Sorry I have not been so active as I once was.. I wanna help but life has been a bit staggering lately. Anyways I come with an awesome free app for all you who wanted to see how I edited my build.prop
I used a program called buildProp editor. It has an easy to understand way of explaining details if each setting you can modify and gives you tips and has a lot of new user help for those who don't know how to use their build.prop
For new users in general, build.prop is basically the phones hardware configuration that allows advanced settings to make slight tweaks to your hardware (this is usually best for personally installed and built kernels, as you get best results out of it vs a stock kernel within the rom). So, this app will provide you an easy method of learning more about build.prop files.
In case your curious, on this phone model I do believe its located inside /system but again, I have a few phones I setup often.
I also use my system tuner pro for more advanced editing but this is not free.. I believe it was $5.00 but it does so much than just a standard app.
I hope this helps you all, because it helped me learn.
Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app
Roni P. said:
Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have more experience with messing with DPIs than I do with kernels, so I'll let someone else answer your question about kernels.
DPI normally stands for Dots per Inch. When it comes to printer, the higher the dpi the smaller the dots and, therefore, the higher "resolution" you get. For Android, though, DPI talks more about the pixel density (I think it's Density Pixel Index, I could be wrong, though). If you really want to get into Android uses this value in their code, the first comment in this post does a good job (IMO) of showing where it comes into play. After all that, the basic correlation is this: lowering the DPI will shrink your icons/apps/etc and effect the way certain apps appear on your phone. The stock GS3 setting for DPI is 320.
The reason people (like myself, running 241 dpi) choose lower DPIs is that certain apps (like calendar, Hulu, Netflix, etc.) have better interfaces on tablets than they do on phones, so we want to "force" them to think our GS3 is a tablet. The "official" way of doing this is by modifying the build.prop file. There's a semi-guide here that you can follow. The main problem with changing this value is that the Google Play Store looks at it to verify your phone. If the phone type does not match the the DPI value, you won't be able to download any apps! There are various fixes to this, but my preferred choice is just to download and install a modified Play Store which allows multi-DPI. Here is the thread for the one that I use (see post #2 for downloads).
Some ROMs also allow you to change the DPI "on the fly" without having to modify the build.prop. I'm currently running LiquidSmooth and in my Settings --> Interface --> LCD Density looks like this. It also has steps that you need to take to make your Play Store work. Having the multi-DPI play store that I linked previously will prevent you from havign to do the "clean up" work, but it doesn't hurt to follow the steps.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Hopefully this is a good primer to see the purpose of DPI and how it's used to customize your experience with your phone.
Let me talk about frameworks and kernels now...
A kernel is the powerhouse of an OS altogether. It is this layer that provides all interfacing with hardware that the OS can then use to implement things like network toggles and such
Everything is defined in the kernel...if something is not defined there, then you cannot use it
This is the reason why building newer roms (from source and not yet supported officially) is difficult because you gotta build the kernel from the ground up. You gotta implement things like Wifi, Power management (voltages, CPU, and proper shutdown and booting up sequences), 4G (if applicable), and 3G
So in summary, the kernel is what provides the software (in this case the Android OS) access to hardware components through this intermediate layer
Now the reason people flash other kernels is because some may manage power better (resulting in better battery life), may implement more features (have more CPU governors or IO schedulers), or provide some extra quality (could be something important like 4G or something as aesthetic as enabling boot animations)
Now frameworks. Each proprietary interface has its own frameworks. AOSP is normally not mentioned when discussing frameworks because it is the "vanilla" or "stock" interface provided by google straight from the original AOSP source that all other proprietary frameworks are built on top of
HTC has its own interface, so does Motorola, Samsung, and LG
HTC's interface is called Sense, Samsungs is called Touchwiz and LG's is called LG UI (very creative, i know ), and i believe, but I may be mistaken, that Motorals interface is called MotoBlur
And each of these proprietary interfaces is primarily defined in the frameworks-res.apk and SystemUI.apk. It is these additions (addition being used in reference to what Google provides) that give each interface its unique spin on things. This is what causes the weather to animate on an HTC phone as soon as you unlock it, what gives the apps a different icon and more features, what changes the icons for the different things in the status bar, what shows recent apps and quicksettings when you slide down the status bar. In touchwiz its the same thing, different icons and other proprietary features like multiview and a more unique keyboard
Basically, the "frameworks" that you keep hearing about is what defines a proprietary interface. It is because of these interfaces that you cannot install proprietary apps or enable proprietary features on AOSP. These things are dependent on the frameworks of their respective interfaces and since AOSP has a different frameworks, then you'll just get FCs and such.
Now I'm not saying its impossible to port proprietary features over to AOSP. It can be done. But its extremely difficult because first you need to track down where exactly these features are defined, and then condense them into either a standalone app, or a series of standalone apps that will behave the same way.
Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app
Roni P. said:
Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I touched upon this in my reply.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Click to expand...
Click to collapse
So basically, the Xposed DPI application allows you to control the DPI on a per-app basis. You can tell Hulu to use 241 dpi and Netflix to use 190 DPI (or whatever you want), even if you have your phone's "default" to be the standard 320 DPI.
In terms of functionality, it'll affect different apps in different ways. A lot of the time, apps won't change at all. Some will stop working, so you'll just have to revert the settings and clear cache and you'll be good to go. It's really up to you which apps you want to modify. A lot of people don't mess with this stuff for fear of breaking things, but Xposed shouldn't have "lasting" effects.
Back when I was using ParanoidAndroid, I had toyed with the idea with creating a Thread in the General forum about which apps look best with modified DPIs. I eventually gave up the idea (was a huge effort while I was creating screenshots of each app before and after), but it might be good to start one up now that XPosed is being included in a lot more ROMs. Meh, maybe once I have a bit of free time.
Dear XDA colleagues,
I recently bought an Android phone based on the MTK6577 engine. In order to improve my skills as developer and programmer, I’d like to develop a new custom User Interface like Sense UI or others. I have my own drawing and transitions already in mind, but I need some useful guidelines in how to proceed:
1) Is Java or C++ the best language to code a new UI?
2) What tools do you recommend to use for best productivity?
3) After Project Butter debuted in 4.1 with enhancements in 4.2, are there any ways to push most of the UI transitions/animations to the GPU rather than CPU? Would that extend battery life?
4) What other coding/system parameters are important to develop an efficient and smooth new UI?
5) What about scalability and easy porting to the future Android releases?
6) If you were to outsource to a SW company such a development, what would be the key requirements (other than cost) you would be asking for?
Thanks very much and looking forward to reading your answers!
Hi all! I hope to have chosen the right section.
I Just wanted to ask this: would be possible to implement Cyanogemod's sound and apps profiles as an xposed module, in order to have them on every rom?
I always use CM-based roms only for profiles, since I can't see no real alternatives (profiles apps doesn't work as well with triggers and are not integrated into the system).
Bye!