In another thread, someone mentioned installing the cyanogenmod google apps on top of a ROM. The apps I am referring to are here:
http://wiki.cyanogenmod.com/index.ph...on#Google_Apps
I had a few questions on this:
1) Is this a good place to find the most up-to-date google apps for my phone? More up-to-date than those generally included with a custom ROM?
2) Is it safe to flash these apps over any custom ROM, or does that depend on the particular ROM involved?
3) Do ROM developers generally make changes to these apps to improve performance or compatibility with the HTC Hero that I would lose by overwriting them with these?
Related
hello there,
i installed Clockword Mod because i wanted to know if it is just as good as the people are talking (managing different Roms) but all Roms that i can see are the 2 CyanogenMod Builds (nighties and Stable)
then Extras
meLianTQ (where nothing is inside)
and the Google Apps
is this really the whole list? Or do i need to change something? Like a sources.list?
Regards
Seelbreaker
That's the whole list AFAIK.
Developers have to ask to get their ROM included in the list.
Firstly, A very Good day to all the awesome people at XDA and my fellow SGS2 users !
To begin with, I am completely new to this scene, so please bear my lack of know-how.
I have a SGS2 GT i9100 and after years of running the stock JB 4.1.2, I have decided to install the new KitKat ROM 4.4.2. So after days of researching I am considering the use of CyanogenMod installer to install the new ROM, since it seems like a safe and stable bet and Philz-CWM as recovery ( Thanks to @Vivek_Neel 's advice ) - Is this a reliable method to move ahead with ?
Also, just to clarify the order doing things - Flash Philz-CWM ( v 6.25.0 ) >>> Then run CM Installer or is it the other way round
Before I do anything, however, I have some doubts which I am hoping to get clarified :-
1) [Regarding CyanogenMod Installer] - Off the many DIY's that I came across regarding installing the new KitKat ROM, almost everyone seems to mention downloading the Main ROM file and Google Apps file and transferring it to the phone before starting.
So If use the CM Installer, do I too need to download and transfer to my phone - the Google Apps and/or any other ancillary files ( if so, which ones ) or will the Installer do it by default ?
2) According to the CM wiki, CM Installer will install a "stable snapshot build unique to the installer. These are stable builds designed to provide all core features and functionality of the device." - What does this mean in layman English ? Also all the guides for installing the KitKat ROM are using "Nightlies" - So which one should I use - What's the difference ?! And will the CM Installer install KitKat 4.4.2 ?
3) Just to clarify, after installing the Custom ROM, will I be able to download and use apps as I was doing when I was using the stock JB 4.1.2 ?
Once again, please bear with my rookie-ness and I look forward to your answers.
Cheers !
Hey guys, I was recently installing a new ROM and kernel on my Nexus 6 when I happened upon something interesting. Franco makes an AMAZING kernel for Nexus devices, and he has an awesome app called FKUpdater which checks his server for new updates to the kernel, provides the user with the changelog for that update, then allows the user to either a) download the zip file for the kernel, or b) download and auto-flash the kernel zip.
I thought this was especially smart because it works regardless of what ROM you're on, since we all know how difficult it can be to stay up to date on both the ROM and the kernel, not to mention any other mods that we like for your phones (thinking back to the pre-Lollipop mods like Xposed, etc).
So, what if there was a way to make a ROM OTA manager, which could check for new versions of your ROM using something as simple as an RSS feed that developers could reference using the build.prop.
Here's the way I imagine this working:
A ROM developer doesn't want to go through all of the unnecessary hassle and costs associated with implementing the OTA features (it's not as easy as it might sound), so instead the developer simply adds a line to the build.prop:
ro.customROMversion.rss=http://www.example.com/rss
This build.prop line would be universal for all ROMs, with the actual RSS link being associated with each specific ROM (so if a development team builds ROMs for multiple devices, they would have one feed per device).
Then the app would check the build.prop for that line, and regularly check the RSS feed for updates. The RSS feed would have a standardized format. It would include the necessary information for the app to detect a new version (version number, build date, etc) as well as including the changelog for the new version (if the ROM developer includes this).
In reality, this wouldn't be difficult at all, and the best part is that the feature could be added in a heartbeat to practically every ROM out there. The ONLY issue I could see running into would be that the download links for the ROMs would (potentially) need to be direct downloads, with no redirects. I don't know how important that would be to implementation, though.
Does anyone see this as being something particularly difficult to do? I would love to build/release this (I REALLY wish I could contribute more to the Android community at large), but I don't know how to program something like this. If anyone thinks they could do this, I would really love to help put this in motion!
Hi.
Is there a way to find all devices that have available stable custom AOSP roms?
I'm looking for a new device, for me and probably family friends, and I'd like to know what can I choose from.
Clean Android is the most priority, ability to choose gapps package, then easy root with Magisk.
Many thanks in advance!
Seeing the issues people are having after flashing OxygenOS & wanting to avoid that myself, was wondering if anyone has had success/problems sideloading GApps on to ColorOS & which package (NikGApps, BiTGApps etc) did you use?
To determine which GApps package is suitable for your specific device and ColorOS version, it's best to refer to device-specific forums, XDA Developers, or other community resources. These platforms often have threads or discussions where users share their experiences and provide recommendations for GApps packages that work well with ColorOS on their particular devices. When sideloading GApps, it's crucial to follow the instructions and guides provided by reliable sources, ensuring you have a backup of your device's data and that you understand the potential risks involved. Additionally, be mindful of any warranty implications or support limitations that may arise from modifying the device's software. AARPMedicare
Is that a ChatGPT response? Anyhow, I just installed the playstore following this guide instead of installing a GApps package:
How to install the Google Play Store on any Android device
It can be tricky, but these steps might just work for you
www.androidpolice.com
Has been working well so far