What do they mean?
I've seen on the repository for HCT android 10 roms for example that there are ones that start HCT2 , HCT4, HCT7 etc. my rom on my device itself says HCT2 but when i 'updated' to a rom the manufacturer recommended me to it now says just HCT. so i'm a bit baffled about the numbers as they don't seem to bear much relevance to versions of the rom etc.
ok then, thanks everyone
I've asked the same question and never received an answer.
Did you want to install them and document your findings here?
Anyone...Bueller...
The launcher looks different on hct4 and 7
Related
I am confused by the many different OS version for WM6 ROMs (20273 22222 19701). I did a search and the closest post I could find didn't really explain the reasons for different OS versions.
Is the latest the best and most stable?
Is there an OS changelist I can view somewhere?
Are the OS versions set by the ROM maker and shared by them?
Are the OS versions set by Microsoft or the device manufacturer that the OS came from?
the only real difference is windows mobile 6 and 6.1
then you have difference in radios provided by different carriers at different locations.
there isn't really a change list since there are only two official types.
if you download a rom from this site it will not be an official rom unless it says it is.
roms aren't updated like windows with service packs, you have to completely "delete" your operating sytem and info and load a new one...... which is why you won't get an update unless it is basically a new operating system.
Renae27 said:
Is the latest the best and most stable?
Click to expand...
Click to collapse
Usually not. Nor are the numbers a guarantee of newness. Sometimes earlier numbers signify newer builds.
Is there an OS changelist I can view somewhere?
Click to expand...
Click to collapse
Not that I have seen. But as Joel said, the only real big difference is 6.0 and 6.1 . Other than that, builds usually feature bug fixes and/or speed tweaks. You are best off to watch the forum for a specific device. Most ROM cooks will post which build they are using, and most new ROMs will use the most recently released OSs. That way you can know the most recently released builds for that are working for that device.
Are the OS versions set by the ROM maker and shared by them?
Click to expand...
Click to collapse
No. ROM cookers (I assume you mean cookers) use various builds which they get from various places. Usually they get these ROMs dumped from recently released models, sometimes they get them because they have connections in the right places; like Microsoft, HTC, etc.
Are the OS versions set by Microsoft or the device manufacturer that the OS came from?
Click to expand...
Click to collapse
Good question. I don't know exactly, but I would assume that an OS comes from a combination of work in both companies.
Thanks for the quick replies.
Does anyone know of any threads that talk about OS version differences?
How does a ROM cooker go about choosing an OS version?
Renae27 said:
Thanks for the quick replies.
Does anyone know of any threads that talk about OS version differences?
How does a ROM cooker go about choosing an OS version?
Click to expand...
Click to collapse
like we said, no there isn't an os version difference.
The differences are 6 and 6.1 or from different phones.
ROM cookers choose ROMs on features they like or what they have available.
A good way to start would be to just find a good ultra lite rom and build from there
Renae27 said:
Thanks for the quick replies.
Does anyone know of any threads that talk about OS version differences?
How does a ROM cooker go about choosing an OS version?
Click to expand...
Click to collapse
well take a look at this thread to understand how a cooker can adapt latest build for his phone
http://forum.xda-developers.com/showthread.php?t=438676
thanx to ameet for the awesome tutorial
Myself and jbelman seem to have the Dev (rooted) firmware based phones that look like they shouldn't escaped Vodafone and been purchased by the public.
I'm curious as to how many of you have the Dev firmware Build number CRA71C like jbelman and myself and how many have the "standard" version Build number CRB17? The more dev phones we find, the better chance we have in doing the customisation that the majority of HTC owners enjoy (lots of clever people on XDA-Developers...).
In case you are wondering how to do this, here it is:
Press the Menu button
Settings
Scroll down to the bottom "About Phone"
Look at the bottom of the screen starting with Model Number and post the info please.
Cheers
Dave
do expect more exploitation on the MAGIC~!
I'm just a CRB17..
And i need to change my fonts. so I need root!
ROOT access is coming
Take a look on this post http://forum.xda-developers.com/showthread.php?t=517006&page=15
elfabio said:
Take a look on this post http://forum.xda-developers.com/showthread.php?t=517006&page=15
Click to expand...
Click to collapse
I think he knows that.... read the post
I didn't before I saw the link so no worries. Exciting isn't it! Roll on proper HTC ROMs! I had looked on the thread earlier but they were still struggling uploading the img. Confused me for a while as it's in the G1 room so never thought of checking. Glad I did now. It feels like your older brother/sister telling you the ways of the world!
Hi all... i have the CRA71C one...
Vodafone Italy (1 week old)
All of my devices are on Test Keys - and I have full root access.
I'm here at Google I/O where about 4,000 Saphires we're given out to all the attendees. All are SIM unlocked and allow loading of unsigned images (confirmed directly by Google Android devs)
Model: Google Ion
Firmware Version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.6.27-00392-g8312baf
[email protected] #72
Build Number: CRB28
Hi there,
I hope I'm posting in the right forum here, otherwise please accept my apology.
I'm new to building ROMs. Currently I'm playing with the HiMedia Q30, don't like their firmware and would like to replace it. At first with alternative ROMs, then with my own build.
I wanted to try SlimRoms, CopperheadOS and LineageOS, but it looks like they're optimized for phones. Even the Oreo builds from the Android website are for phones.
Questions:
1. Do the mentioned ROMs work on any device?
1.1 If so, why are they optimized for different models?
2. Can you recommend a ROM for TV boxes?
3. Is there any general Android (preferably 7+) build that works on any device?
I appreciate your help. Thank you.
AB
any luck with this yet?
Hello...I'm trying to get Android working on an older tablet/laptop (Dell Venue 11 Pro i3). No matter which distro/version I try (and I've tried lots, both custom releases and the Android-x86 project), I always end up with no wif or bluetoothi. Android installs and runs no problem every time, but without connectivity...
I'm a newb with this but not with PC tech in general. I assume I am missing a fundamental step in how to install and configure/add wifi support but I can't find a comprehensive set of instructions or even some rough steps as to how I can add support for my wifi chip (Intel).
Can anyone point me to some good reading that will educate me on how to do this? (...or just tell me I'm SOL if it doesn't work after installing)
Thanks much. I've been trying to find this information for many days now for fear of it being something that's obvious to everyone else.
Kevin
hulakai said:
Hello...I'm trying to get Android working on an older tablet/laptop (Dell Venue 11 Pro i3). No matter which distro/version I try (and I've tried lots, both custom releases and the Android-x86 project), I always end up with no wif or bluetoothi. Android installs and runs no problem every time, but without connectivity...
I'm a newb with this but not with PC tech in general. I assume I am missing a fundamental step in how to install and configure/add wifi support but I can't find a comprehensive set of instructions or even some rough steps as to how I can add support for my wifi chip (Intel).
Can anyone point me to some good reading that will educate me on how to do this? (...or just tell me I'm SOL if it doesn't work after installing)
Thanks much. I've been trying to find this information for many days now for fear of it being something that's obvious to everyone else.
Kevin
Click to expand...
Click to collapse
You need to make sure that whatever OS you are installing has the correct OS and correct kernel that is built specifically for your device's model number. The kernel is what allows the software to use your hardware, kinda like drivers on PC, if the kernel isn't correct, your hardware doesn't work correctly, regardless of whether the OS works or not.
You need to be using your specific model number to find a compatible ROM/OS for your device.
What is your device's specific model number?
What android version are you trying to install?
Sent from my LGL84VL using Tapatalk
Droidriven said:
You need to make sure that whatever OS you are installing has the correct OS and correct kernel that is built specifically for your device's model number. The kernel is what allows the software to use your hardware, kinda like drivers on PC, if the kernel isn't correct, your hardware doesn't work correctly, regardless of whether the OS works or not.
You need to be using your specific model number to find a compatible ROM/OS for your device.
What is your device's specific model number?
What android version are you trying to install?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I realize now that I've posted in the wrong place....but I'm referring specifically to Android-x86 and the many variations out there (Remix, Prime, Android x86 Project, another whose name escapes me right now).
I've never seen hardware specific versions of Android x86, but I've always wondered if users need to recompile the kernel for their specific hardware...yet I've never seen that mentioned anywhere.
I don't think I have hardware that's super obscure. Dell Venue Pro 11 (7130 MS)...i3, Intel HD4000 graphics, Qualcomm/Atheros/Dell 1537 wifi/bt. The most recent version I tried was 8.1 from the Android-x86 project site. Each variation I try runs fine in every other way, but without connectivity.
Hello all!
First time poster, just getting into rom porting and android dev.
making this thread, due to the serious lack of information / boards about these tiny china phones that are flooding wish/aliexpress and are stuck on android 6.0/7.0.
I've tried to use a few different roms as ports (where i patch select files from etc/lib and all that good stuff) using a guide found here specifically for mtk chipsets. I've only tried x32 to x32 same SoC, and patching kernel from stock rom in. This was without any kernel changes, still patching in my 3.18.19+ kernel over mostly 7.1.2 roms built for 3.18.19. I'm guessing the + makes it completely different like mt6737 vs 6737t or 6737m.
My goal is to port an MTK kernel to my current device (soyes s10, mt6737m android 6.0 kernel 3.18.19+ 3/32gb model) that supports android 7.1.2. I've found what I believe to be an almost the same version device tree, and I have ubuntu and windows and am rather well versed in both.
I'm not sure how to discern the kernel version (linux ver) of this download, but my "custom build version" is looking very similar, alps-mp-m0.mp1-V2.84_bd6737m.35g.b.m0_P81.
I'm mainly wondering:
1. Who else has some of these tiny china phones (only band 41 us support!) melrose, ifosa, soyes, unbranded, etc? I've ported over TWRP for this device also if anyone is interested. root was simple enough with mtk-su. It flashes zips but it wont boot roms. it's TWRP 3.2.1.0 or 3.1.2.0 I'm not 100%.
1a) could my whole problem be solved by porting a newer version of TWRP for the device?
2. can I port newer kernel 3.18.35 from source above?
3.MTK's whack implementation of fast charging, PE+ 2.0 support for my mt6737, they send 15w (5v3a) motorola branded charging brick with phone. but it seems to charge at random rates, not fast charging. Not sure if it's even worth it to try and find a brick that is listed as MTK PE+ compatible. anybody have any advice there? it would be a dope phone if the fast charge was reliable. maybe I can mod the kernel to force enable it in the future.
4. why won't any of my ported roms boot? I can't find a modules folder in my stock fw's lib image(s) where it should be in order to port. are these maybe just located in the root of /lib and very specific files I have to cherry pick and port over? i'm thinking android -all modules = no booting. not really sure where i'm going wrong but it's a million questions in one so if you can answer any of them, please chime in
I forgot I can't post any links, but like I have links to stuff
Thanks guys, I've been lurking these forums for near a decade.
It's nice to meet all of you, looking forward to some good learning
Nick
Hi mate.
First off, I'm really sorry -but I can't answer any of your questions...
I'm looking at the Servo S10 for myself, though ; how did you go with everything -any progress?
Also, how is the battery life? Sounds like it's not a deal-breaker. Sorry again that this isn't an answer to your questions, but I'd appreciate the feedback.
-anew