I was just looking through build.prop and thought to myself that I could put whatever I wanted to in the Android version and Build number fields. My Android version is now my name, and the Build version my address.
But you could put whatever you want there, so why not tag your phone? I am sure you guys could come up with something much more cool to write....
Related
Help Me Understand Android Build Numbers
Android 2.3.6
Build Numbers CR-T463_B01-S01_V02_20120925
fuct26 said:
Help Me Understand Android Build Numbers
Android 2.3.6
Build Numbers CR-T463_B01-S01_V02_20120925
Click to expand...
Click to collapse
Android build numbers for AOSP based ROM's and Nexus Devices follow a standard naming convention which you can read more about here. However, most non-Google devices use the device manufactures own build number system which does not have a standard syntax or naming convention. In essence, each manufacturer usually chooses there own naming scheme which works for them and it isn't always easy to figure out how they came up with that naming system for the build number. Try to interpret your build number of CR-T463_B01-S01_V02_20120925, the B may stand for base or build, S may stand for server (As in build server), V may stand for version, and the 2012925 likely refers to the date the build was produced which in this case would be September 25, 2012 (9/25/2012). Overall, most non standard build number designations often refer to a companies internal naming system that can be difficult or near impossible for someone who doesn't know the naming system to figure out.
thank you
Hello,
I'm checking the official list of android build numbers on the android homepage ( http://source.android.com/source/build-numbers.html ), and I find some things strange..
First one, why is the build number ITL41D repeated for android-4.0.1_r1 and android-4.0.1_r1.1? isn't this a typo?
Secondly, When I got my Nexus 7, It had pure android 4.1 and the build number JRN84D, but that build number doesn't appear on the list?
Third, related to the second question, I don't find android-4.1_r1 on the list, which may be why JRN84D is missing, but I also can't find android-4.0_r1.. anyone knows why are those missing?
Fourth, cupcake wasn't using build numbers?
Thanks everyone.
Noone knows?
up
Hi all,
I am looking to find a way to build from repository the latest camera/gallery combo and email/calendar from 4.4 in a CM10 (4.1.2) build process. I get the error that I am building a version of Android too low to use these resources. I have the default set in the repo manifest, and a build version in my cm.mk file. I have tried to a simply chang the fingerprint to 4.4.2 and then adjusting the build number. I also changed the repo version to sync with but it still wants to build 4.1.2
I keep getting into trouble with different local settings in jni files etc. Has anyone managed to do this successfully or is it always a case of cross your fingers and copy the apk in after the build. Ideally I would want to avoid this as I want to make it rather than mka and get a nice ODEXed set out.
Any help very much appreciated
The reason why nobody else is doing this is because it's really improbable you get this working.
For this to work you have to port most of the stuff that makes 4.4 version 4.4 back to your CM10.
It would be way easier to compile 4.4 and change the undesired apps back to CM10 apps. Because 4.4 does have the API and features that CM10 does, just not the other way around.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
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!
I Have a phone with a custom ROM and can't determine the phone model and can't find other ROM for it.
This ROM is somehow anoying because some ads popup and because I timezone is always set to China:
https://forum.xda-developers.com/android/software-hacking/timezone-to-china-t3704685
I need to know how to pick the current ROM/Firmware, change apps and configs (the bonus is to create a vanila pure android image) and then flash it again to the same phone.
I don't want someone write here HOW to do it. Just point me to softwares and tutorials. A start point I can walk by myself.
I have huge skills in Java and Ubuntu. Some skills in flashing images to NAND (bacause my work on Cubieboard) and already changed the ROM of my other phones and tablets.
My phone shows me this information:
Code:
Sony Xperia C6 Ultra
Android 6.0
Kernel 3.4.5-526212
[email protected]#1
Build number 23.0.1.A.5.77
Custom Build version
ALPS.L1.MP6.V2_GXQ6580.WEG.L_P69
I know this is not a Sony device but have no way to discover more about it.
Can I start from here?
http://www.teamandroid.com/2017/07/16/download-mtk-img-extractor/