guys i was thinking recently that all apps in android are modular i.e. they manage to fit themselves in any phone of different resolution or configuration,the same version of a particular app runs fine even on a low budget phone as well as a high end phone and sometimes even on tablet.the roms are comprised of many such apps ,android is modular and everything even lockscreen and settings are apps.
My point is if a single rom can be made which will be compatible with maximum number of mobiles . i do realise that there may be a few problems with wifi, bluetooth and maybe camera .but the first step is to get the rom booting.and of course kernels will have to be different for different devices,and maybe the problems with wifi can be solved by flashing kernel specific modules.
if this concept is feasible then the effort of porting roms and uploading them will be negligible .
if you think that this concept is new and innovative please reply and hit the thanks button
Related
Q&A for Unofficial CM11 for Saga [06.10.14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hello! I have my Desire S for more than 3 years and it's really wonderful that it has fresh updates thanks to you guys! Great work! Maybe one day it'll be Lollipop also on our device
I've been using cm-11-20141006-UNOFFICIAL-saga for about 2 weeks, it had "no camera" error, some lagging, but it hadn't "mic error", wifi, gps problems or something else and all in all it was good for a daily use. Then I decided to flash the latest build - cm-11-20141020-UNOFFICIAL-saga and from the start it has problem "Unfortunately, the process com.android.phone has stopped"
I will test your new builds as possible and very glad to help you.
com.android.phone
Installed the latest version of CM11 works, but again an error "com.android.phone".
com.android.phone
Installed the latest version of CM11 works, but again an error "com.android.phone".
what to do?
Issues
cons:
Other person cant hear me during call (in loudspeaker mode everything is alright)
Front facing camera is just fliped 180 degrees back camera
signal stucked at 1 bar
themes tendt to crash but nothing special
dolinh said:
cons:
Other person cant hear me during call (in loudspeaker mode everything is alright)
Front facing camera is just fliped 180 degrees back camera
signal stucked at 1 bar
themes tendt to crash but nothing special
Click to expand...
Click to collapse
There is ver.2 for testing
During development MoKee for DS, I do not know how Ruling solved the problems on warning no text context during flashing Rom and Calling problem on his ROM development. I remembered he has the same problem on version prior to date 08/08/2014.
So far CM11-2014-10-24 is providing users with fast responsive, smooth and stable, however, it is still contained some bugs considerable minor for me in comparison to the mentioned functions. On top of that in SuperSU, list of managed apps which require SerperSU granted is easily shown up when open SerperSU of which none of CM11s for Saga has provided even popular CM11-MoKee 2014-08-09 which provides users with responsive, smooth and rather stable is still not provided this feather which I consider as important as other. If the ROM is not providing the feathers as it is supposed to be, there should be some bugs preventing that feather to normally function. However, considering the machine itself is also far from perfect when using ROMs that it is not orginally assigned for, bugs is not avoidable; besides ROM software itself has to be developed to suite many kinds of apps from various developers. So developing software for variety of favourite is a hectic task. Android phones, for me, small ROM with small algorithms with less complexity should be a good ROM since it provides a direct access rather than going around. I have been testing many kinds of ROMs including sens, JB and Kitkat for a while and decided to stick on Kitkat rather than sens or JB. For old machine like Saga, if users could ignore some minor bugs and battery drainage in comparison to sens or JB , Kitkat is considering a good choice of ROMs around. I mainly used MoKee by Ruling after Devin Kin stop his development and found that the ROM still has some bugs such as list of apps allocated by SeperSU did not shown up and occationally lag and hang up. I found this version of ROM kindly developed by Kylon and sHAKajaada has suite my needs. Thank you very much.
Remix151 said:
Is cm-11-20141028-UNOFFICIAL-saga.zip fixes ringtone_fix_flinny_a5?
Is everything on this point is working or further need to apply this patch?
http://forum.xda-developers.com/showpost.php?p=51318467
Regards and thanks for your hard work!
Click to expand...
Click to collapse
It is working by itself, there is no need to fix, calling can be heard on both sides. Kylon has compiled with his fix though. The problem, I have so far is Wifi Ap, I could not figure out how to enable it, because Kylon has disable WiFi Ap.
here
kchaisu said:
So far CM11-2014-10-24 is providing users with fast responsive, smooth and stable, however, it is still contained some bugs considerable minor for me in comparison to the mentioned functions. On top of that in SuperSU, list of managed apps which require SerperSU granted is easily shown up when open SerperSU of which none of CM11s for Saga has provided even popular CM11-MoKee 2014-08-09 which provides users with responsive, smooth and rather stable is still not provided this feather which I consider as important as other. If the ROM is not providing the feathers as it is supposed to be, there should be some bugs preventing that feather to normally function. However, considering the machine itself is also far from perfect when using ROMs that it is not orginally assigned for, bugs is not avoidable; besides ROM software itself has to be developed to suite many kinds of apps from various developers. So developing software for variety of favourite is a hectic task. Android phones, for me, small ROM with small algorithms with less complexity should be a good ROM since it provides a direct access rather than going around. I have been testing many kinds of ROMs including sens, JB and Kitkat for a while and decided to stick on Kitkat rather than sens or JB. For old machine like Saga, if users could ignore some minor bugs and battery drainage in comparison to sens or JB , Kitkat is considering a good choice of ROMs around. I mainly used MoKee by Ruling after Devin Kin stop his development and found that the ROM still has some bugs such as list of apps allocated by SeperSU did not shown up and occationally lag and hang up. I found this version of ROM kindly developed by Kylon and sHAKajaada has suite my needs. Thank you very much.
Click to expand...
Click to collapse
The feature on SuperSU of which I mentioned that app permission list is not function on CM11-MoKee 2014-08-09 now is working perfectly after updated to new version of chain fire. This problem should be related to SuperSU itself.
Installing CM11 on HTC Desire
Funny thing my answer seems to go to a different thread, but nevertheless...
In the "Unofficial CM11 for Saga [06.10.14]" thread ManishGade described a blank screen after installing CM11. That may happen when boot.img has not been flashed, especially if there's a stock ROM there.
Moving from stock ICS 4.0.4 to CM11 on HTC Desire S:
1. Unlock bootloader (HTCDev etc)
2. Download cm-11-xxxxxxxx-UNOFFICIAL-saga.zip
3. Replace upload-binary (inside the zip) with patched version, or you'll get "set_metadata_recursive" error (see this thread: http://forum.xda-developers.com/showthread.php?t=2532300)
4. "fastboot flash recovery recovery.img", with 4EXTRecovery_v2.1.3RC4 (none of 1.0.0.6 I found worked for me - the screen stuck on "HTC", that's why the trick with upload-binary was needed) - http://www.4ext.net/get.php?f=4EXTRecovery_v2.1.3RC4.zip&device=saga
5. "fastboot flash boot boot.img" with boot.img from the CM11 package
6. Go to the 4ext recovery (battery out/in, VolumeDown+Power, Recovery)
7. Wipe data, clear caches, install the CM11 zip package.
Regards,
Thanks I installed it last monday.
When my waranty on my desire ran out I installed Cyanogen 7.2 even though it is old it is brilliant. Last Monday I decided to install CM11 unofficial for Saga. Also a Brilliant Rom!
Every time there's a new Android version released, rom developers start from scratch.
So for example there could be lots of options the developers made in the last version. Now they have to do it all over again for the new version. Many times all the previous options are missing or dont work right.
As a real example, my last rom version was AOKP 4.4.4. I am now looking for a rom based on 5.1 with all the options I used to have but I cant find them. All the debugging and programming has to be done from scratch again and the whole painful cycle of providing CatLogs and getting bugs to work out and updating the rom starts again.
Why does it have to be like this?
Why cant there be a modular software design? We have CPU, memory, a screen, volume rocker and other hardware. Why cant it be plug and play?
Hey, am I the only one who feels like each of the latest Android Versions from 4.0.2 until Lollipop were steps backwards?
I remember when i started experimenting with 2.3.5 and there, it was Raw, you could feel that the device got so much more power and possibilities after flashing, par example Cyanogenmod compared to the stock roms.
But i expect now (was one year without Android, sadly) that the latest versions are now so complicated to modificate. On CM7.2 you had so many settings in the Settings section. Now you need to flash a framework (so many frameworks for so many devices, OS, Versions and so on) which are buggy, lagging and device slowing. After the Framwork you look for an APK to be able to download extensions for the framework to chance setting from the system (the version the extension is made doesnt even matter now, because the framworks you flash are so different that the android version kinda doesnt even matter).
Now, we are on 5.1.1 and it feels not true anymore, it is hard to use devices still without google apps, even on CM7. Many apps need a connection to Google, like Snapchat to even work.
The Hardware of devices exploded, is so high now that we don't give a #### about the software anymore. I remember, on my old device HTC Incredible S, we had so many developer who builded over 30 different kernels, changed so many things from the rom, trimmed it, even the code to made them as fast as possible, with every setting you need in the section it fits, many different flashable extras integrated in the rom with an ON/OFF Switch (Now it's more like Aroma gets interesting, but getting always back to Recovery, Flashing the Rom again for some extras?)
I feel like android is lossing itself. What do you think?
Hi guys! I have quite a few questions, and I specifically didn't find any answers to mine. If you people can describe the answers to my questions I will be very grateful or give me links to where I might find answers is equally appreciated.
1. Can any ROM be used in any device?
2. What makes the same ROM different for different devices and why, say two phones having same specs and features even ?
3. I previously used a LG L70, now I'm using a Lenovo Zuk Z1, former I flashed a CM13 nightly, later came with a Cyanogen OS 12.1. The ZUK has less customization options than the CM13, at this moment I can only remember that ' Control Vibrator Intensity ' is missing. Why, is it due to different phones or COS and CM difference?
4. I don't know anything about separate kernels for android, if anyone could shed some light?
5. Custom ROM , Custom Kernel, difference ?
6. There are a lot of ROMs out there, anywhere I can find actual comparisons ? Found a YouTube video of 'Master ROM Cup 2015', in Italian, so can't really say anything about quality or authenticity
7. (i) Exposed Framework, Custom ROM, difference, advantage, disadvantage ?
(ii) I want a plethora of customizations, fingerprint sensor compatibility, better than average battery life, any recommendations ?
8. Don't know of this is a ZUK Z1 issue or COS issue, the phone has dual sim card capability, but what I didn't find is option to use Cellular Data option selection for the sims, only the data of the one inserted at sim 1 can be used, and though I have selected the option to ask to select Sim before calling, it is calling from a random Sim if I select a contact, only gives me option to select sims when I dial the whole number and press the call button !!!!!!!
Thank you Sir/Madam for reading my long post, any help will be highly appreciated.
I can answer a few of these for u-
1)Any ROM cannot be used on any device as a ROM has to be made for that particular device else the phone will possibly get bricked.
2)This could be due to the architecture difference or the components used to ensure same performance (processor,GPU, RAM etc)
3)CM13 is a mod while CMOs is an is built by the cyanogen company for the public. So the features might have been reduced.
4)A kernel is basically a part of code which runs to ensure that apps get executed properly, have enough storage space and other parameters.Different ROM's have different kernels and u can also flash kernels.
5)Custom ROM is a separate image while a custom kernel is a different part.u can flash both independently and generally custom ROM's have a custom kernel.
7)exposed framework is used to again enhance the features your current ROM might not have.Its just a set of tools made for this.The advantages would include better performance, customisation etc and the disadvantages would be that the phone could be more vulnerable to security issues.
8)from what I can tell,this could be the way the ROM is designed so as to allow data on the first sim and the same could be for the sim too.
Sent from my Moto E using Tapatalk
Cruzy12100 said:
I can answer a few of these for u-
1).......
8)from what I can tell,this could be the way the ROM is designed so as to allow data on the first sim and the same could be for the sim too.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Didn't understand the last answer mate !!!!
I usually root my phone and install custom ROM to customise my phone, what else does a custom kernel offer ??
A custom kernel basically offers you different governors which can alter the way programs are executed and using custom can lead to better performance and battery savings.
Sent from my Moto E using Tapatalk
Here Are The 3 Reasons Why Your Phone Slows Down Over Time
Today almost everyone holds an Android smartphone. If we talk about an Android operating system, it is now powering the majority of smartphone nowadays. On Android, we keep on installing different apps and games.
However, after six months of heavy usage, a loss of performance is spotted in every device running on any version of Android. Today we will not only talk about Android because the issue is present on iOS too. Users on both sides complain about their phones just aren’t as fast as they once were.
There are many potential causes, which makes our smartphones to slow down after several months. So, in this post, we are going to describe 5 common reasons which cause our phone to slow down after few months of usage.
1. The OS Upgrades
Just remember, when you first bought your device, it might be running Android KitKat or iOS 7 that time. Both iOS 7 and Android KitKat were launched in the year 2013. Well, these upgrades are released with a certain set of hardware specs in thought.
If we take a look at the current year, hardware specifications have drastically updated. Many features have been added in both iOS and Android. However, these features are made with newer hardware specs in mind. So, if you are running the newer version of any operating system in an outdated phone then this can slow down your phone in no-time.
However, these upgrades are hard to ignore, so minor updates are okay, but if you are planning to jump from Android KitKat to Nougat then be ready to face the difficulties.
2. App Updates
As we already mentioned, we keep on trying new apps and games in our Android and iOS devices. The so-called ‘lightweight’ apps that you install can be transformed to ‘heavyweight’ over the time. The main reason behind this is app updates. Developers are constantly pushing updates, every new update brings new features, which ends up eating lots of RAM and CPU.
The best thing you can do is to once you feel the app is bloated, replace it with another light weight app.
3. Apps Running On The Background
Other crucial things that we neglect are the background apps. Believe me or not, you have almost 80% more apps installed on your devices than when you first got it. Just go to phone’s settings and have a brief look at all of your downloaded apps. Users might think that they have installed 10-15 apps, but are often shocked to see closer to 40-50.
The problem arises when some apps keep running in the background without activating it. There are many apps like email services, messaging apps which are always active. These apps use CPU and RAM, which impacts your phone’s performance.
So, make sure to disable or uninstall the apps which consume lots of RAM and CPU, switch to static wallpaper and say goodbye to live wallpapers.