Hi All,
Seeing as the source code for the M8 sense and GPe's various open source components has been released for over a month now, why havent we seen any source built ROMs yet? Things like a Paranoid port or a CM11 port would be welcome on our devices (i know not all of you want it but some of you certainly do). I ask because i am considering building something from source for the M8 and modifying various aspects in order to solve what i perceive as the problems with Android on our device.
Kind of half expected a Tizen or Ubuntu Touch port in the pipes at this point also. But its probably early days for that.
Cm is being worked on for the m8. Most of those roms are based on or use components of cm so I imagine once cm puts a working rom up many more will follow.
Sent from my HTC One_M8 using XDA Free mobile app
Related
HTC Releases Desire HD Source Code
For those of you with an HTC Desire HD, today is a good day for you! HTC has released the opensource bits of the Desire HD's source code on their developer website (see below for link). The most important parts of this release are the kernel and the drivers for the phone.
With the kernel and drivers code developers and tinkerers can start building custom ROMs for the device, making it go faster, the battery last longer, and who knows what other sorts of cool stuff! This won't happen over night, but now that the code is in the wild, it's just a matter of time.
And for you guys that would never, ever run a custom ROM on your phone, you've got good news, too! The more sets of eyes looking at the source code, the more likely it is that bugs will be found and fixed. This means that your devices will likely get more stable and bug-free the longer the community digs into the code.
http://pocketnow.com/android/htc-released-desire-hd-source-code
has anyone played around with the desire hd rom and got it working fully on the desire yet ?
Check the development section, there are already ports, only the camera doesn't work but other than that everything is perfect.
But with this Source Code we will maybe se more stable HD roms + working camera?
Hi everybody, I'm considering buying an One X and was wondering what's the state of future updates as far as AOSP/AOKP goes.
I'm asking because I currently have Galaxy S2 which gets all the new Android releases from cm/aokp but has some problems due to the kernel source code not being published for the Samsung made Exynos chip - from what I understand it makes coding very difficult and a lot of rom coders stay away from the device and move to newer and easier phones to code for.
Does One X has a similar problem making it's life span shorter in terms of Android releases or no such problem and I should expect new Anroid releases for the next few years (not official but AOKP)?
Thanks ahead!!
https://github.com/MiCode/
The project call patchrom，we can just make a build with the cm rom or our official sense rom.
I want to hava a try but i have not learned to do it.
There are so many miui fans still using inc.
So, any developer can try this out?
Tiny? Pons?
However, thanks for your cm10.1!
Due to me having to build on a build bot, then downloading a compiled ROM taking over 2 hours on my slow internet, I don't see me trying this right yet. Or at all. I'm not too fond of MIUI; I prefer CM, obviously. Plus I glanced at some of the code and, most (all?) of the README's are "This is a place holder, please fill in real text when you add stuff." for the past 3 years. I'm not too big of a fan of undocumented ROMs, and they don't even really have a basic readme. I also didn't see a readily available inc device tree, though admittedly I didn't look too hard, so this might have to be a port, than official compiling.
Galaxy S3 Rocking CleanRom 7
kyle1087 said:
Galaxy S3 Rocking CleanRom 7
Click to expand...
Click to collapse
This post is unrelated to the Inc.
Sent from my HTC One using Tapatalk 2
So I'm not a developer or anything, just an enthusiast.
I was wondering something.
ROMs often don't get updated because support of the chipset has been dropped. I'm guessing this is like a driver?
If it's the same hardware, why does it need a new one? What changes in each new version of Android that means it needs a new one?
Also for those that have lost support, some devs still make ROMs. How? Do they make one themselves somehow?
I'm going to look really stupid if this is wrong.
Thanks!
Sent from my HTC One X using Tapatalk
tomhurst said:
So I'm not a developer or anything, just an enthusiast.
I was wondering something.
ROMs often don't get updated because support of the chipset has been dropped. I'm guessing this is like a driver?
If it's the same hardware, why does it need a new one? What changes in each new version of Android that means it needs a new one?
Also for those that have lost support, some devs still make ROMs. How? Do they make one themselves somehow?
I'm going to look really stupid if this is wrong.
Thanks!
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
This is what I understand, correct me if I am wrong.
Think Windows XP & Windows 7.
Can you use the same drivers?? maybe some but not all, since newer implementations are there (graphics stack updates [DX9 vs DX11]) that require newer drivers to work with. Especially with graphics. Even though the kernel is opensource, certain proprietary components are closed source and are always provided via precompiled blobs(Reason: It may expose proprietary IP to the competition) that will work with the version it was compiled for but not newer ones. Even documentation on these blobs are minimal to non existant.
Sadly, these blobs are the main issue and a lot of workarounds are implemented by our great devs to make older blobs work with newer android releases but at a penalty of stability loss and/or performance issues i.e HTC OneX 4.2.2 blobs are being used for 4.3 & 4.4. Sometimes if your lucky then a different phone with the same hardware is updated to a newer version with newer blobs which can be used.
Sometimes such issues escalate so much that opensource devs are driven to reverse engineering(Really difficult!!) drivers and develop opensource variants. One such example is the nouveau project on desktop linux. nouveau is a reverse engineered opensource nvidia driver and at its current state is very stable but sadly its for the desktop. Recently you may have read that nvidia is adding support for their upcoming chipset i.e Tegra K1 by adding their own patches to that driver.
Such a positive step from nvidia was recieved with great praise by the opensource community... even the ultimate Linus Torvalds himself
Article: https://www.xda-developers.com/andr...ger-salute-from-linus-for-doing-things-right/
Eventually lets hope when nvidia has no use for T3 IP that they opensource all components and they provide a way for newer drivers to be built but sadly by that time the T3 would be too old.
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.
Source already available
We should wait for devs to build it ?
AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.
Yap, waiting for you too @joel.maxuel for working on it
allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.
Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0
Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk
The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,