Related
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
aokp is good man...there is no difference
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Thanks everyone.
simms22 said:
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
Click to expand...
Click to collapse
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
[email protected] said:
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
Click to expand...
Click to collapse
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Ace42 said:
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Click to expand...
Click to collapse
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
the information is there, screenshots arent needed. but you should stay with cm then, if youre looking for an op and not a rom.
anyways, you do realize that all the nexus 4 roms are built from source? there no need to port roms to any nexus since all the sources are available for every nexus. so to say, all nexus roms are built specifically for the nexus 4, even cm. just because a rom exists on multiple devices, doesnt mean that its ported. most non nexus roms are ported to non nexus devices because they dont have sources available. this doesnt happen to nexus devices.
this is identical with a thread i remember seeing in the gnex forums a while back. anyways, they are all made for the nexus 4. they use drivers that are specific to our phone. if you flash it on another device, it wont work. AOSP is AOSP, that's the point of it. you won't get any extra device specific features if a rom is only built for the nexus 4 vs cyanogenmod which is out for a bunch of phones. the only way that happens is if your phone has a hardware feature another one doesn't ie: NFC.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Hi. There are many things to argue here is this post but I will try to help to get you some information to get you on the right track. First off there are two versions if you will of Android, one being "AOSP" or the "Android Open Source Project" and "Google Android". Google Android is what shipped with your device, and has Google owned proprietary in it that is closed sourced, most of the development done in a Nexus forum will come from using AOSP Android. Its the same Android that ships with your device but it does not contain any of Google's proprietary and its completely open-source, however some of the coding needed for a specific devices hardware is not open-source, there's more I can go into on that but I'll stop in short by saying the Nexus4 is probably one of the best devices to be working on platform level coding since all of the binaries needed are properly licensed and most of the hardware coding is open-source. So now that's out of the way. Most of the roms here are forks of AOSP with some being forked from AOKP, CyanogenMod and PA, in order for a developer to build a Nexus4 rom they have to use the provided hardware binaries in combination to the software coding to produce said roms, so ALL of the roms here are built directly for this device. Where confusion come in at is that some of the developers do not have a Nexus4 and build based of the availability of someone being a guinea pig. Also you will have to know whats in you device, such words as "krait optimizations" should not be a hook to get you to try a rom nor should a screen shot since most of the roms look stock besides the few that are themed, ok if they're themed they probably should have a pic, but seriously know your hardware so that you are not just letting a buzzword give you a placebo effect, and remember a roms OP most times doesn't do any justice for the experience you will have from that rom so its best to just try what ever sounds interesting blindly...
TheeWolf said:
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Click to expand...
Click to collapse
you can't really optimize a rom for a specific device.
they are nearly the same for all devices, and there is no point in optimizing it for specific hardware.
what you can optimize is the kernel, the part that contains the device specific drivers and basically controls the hardware. these are already built and optimized for the nexus 4.
but that doesn't mean that fixes and improvements for other devices have negative effects on the nexus 4.
also, device specific changes in changelogs are mostly kernel related.
TheeWolf said:
Thanks everyone.
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
Click to expand...
Click to collapse
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Thank you everyone for the explanations.
gee2012 said:
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Click to expand...
Click to collapse
As I have said, I have already flashed many ROMs, I am not basing my opinion on nothing. I have not opened this thread is not to find out "what is the best ROM" - more than a year of messing with Android and being here in XDA got me understanding there is no such thing, no best ROM. The purpose of this thread is get me some answers, to see if what I am saying is even true.
If Cyanogenmod is the same for every device then riddle me this:
Why is there a different .zip for each device?
You are not going to find a better all around ROM than CM dude. In CM each device has its own tree with many device specific commits and custom changes. You sound very ill-informed asking the questions you are asking; I am surprised you haven't received a lot more flame for it.
Hello. I have written an app that helps to improve the accuracy of the S-Pen. It works only on Note phones because Samsung has compiled some S-Pen device driver interfaces out of the tablet ROMs. It is not clear why they did this. I have asked Samsung but gotten no replies. I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). It seems that the tablets suffer from the same issues related to the S-Pen as do the phones and I have many people asking me to make my app work on their tablets. I cannot do so with the stock ROMs because of the missing interface files.
So I am wondering if there any non-stock ROMs in which the S-Pen is more fully supported. The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation. If anyone knows of any ROMs for the S-Pen equipped tablets that provide these interface files, I would appreciate knowing and may be able to direct some folks to using them.
Thanks
I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack
JSale said:
I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack
Click to expand...
Click to collapse
Jack, some replies to postings in the Note 8 section indicate that the two files are present on the stock ROM there. Interesting... I am downloading a dump of the 10.1 now to see if I can see anything. Thanks
Any progress on this? It looks quite promising in the note 8.0 forums.
Regards
Jack
whitedavidp said:
I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). ... The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation ...
Click to expand...
Click to collapse
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1
kcrudup said:
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1
Click to expand...
Click to collapse
Hello and thanks for responding/helping out. I am certainly no kernel programmer. But I have downloaded the kernel sources for a couple official Note devices/versions. I have been reading files located in kernel/drivers/input/touchscreen/wacom paying particular attention to the file wacom_i2c.c. I cannot help but note that some of the functions which appear to reference the driver i/o files that are missing are #def'ed out of certain devices - see line 837 #if defined(CONFIG_MACH_P4NOTE).
I have no idea if the Wacom devices used in the various Note models are the same (except for size) or are similar enough to be treated as the same by programs like mine. Heck, I am not even sure if Wacom devices are being used in all the Note models. So I am afraid I am not much in the way of technical help here.
What I do know is that some custom ROMs for Note I and II phones seem to have been created with drivers that DO support and create the needed driver i/o files but which lack the device settings and other mechanisms which actually take advantage of these i/o files. Basically, they do not offer a dominant hand setting nor do they seem to communicate to the Wacom device when an orientation change is detected. I have been able, through my app, to compensate for these lapses on those devices and thereby improve the SPen's accuracy.
I have had users wanting to get the same effect on Note tablets with my app. So I presume they are experiencing the same type of problem on their tablets that I experienced on my Note I phone that led me to get into all of this. But I know that my app cannot help them unless the i/o files are there.
I was surprised to hear, over in the Note 8 forum that the files do exist on those devices. I know from a tester that my app at least runs on the Note 8. But I don't know if it helps any since that tester was not seeing the problem my app is designed to fix. But I read here that the files are not on the larger Note tablets. I don't know why and have asked Samsung and get basically no answer. My underlying assumption is that the Wacom devices are basically the same but I cannot answer why Samsung treats them as different.
I am sure all of this doesn't help much. Sorry. All I would like to do is try to find a way to offer support to the tablet users who want it.
Cheers!
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Im going to quickly revert from baked to android revolution to test this
I will let you know what I think.
Regards
Jack
JSale said:
I'm going to quickly revert from baked to android revolution to test this
Click to expand...
Click to collapse
No, this is just a kernel- you won't have to change distributions to try this.
kcrudup said:
No, this is just a kernel- you won't have to change distributions to try this.
Click to expand...
Click to collapse
But baked is based on CyanogenMod, unless this kernel is compatible?
kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Sadly, I don't own one of these tablets (yet). But I have passed this on to a user who previously asked me (and got this thread rolling as a result). So perhaps he can check it out and try my app on it. If he does, I will certainly report back here. Thanks for your efforts.
JSale said:
But baked is based on CyanogenMod
Click to expand...
Click to collapse
Oh, then yeah- as I suspect CM won't have any of the SPen goodies. My bad.
In any case, let me know. It was a very trivial fix and didn't appear to break anything. I don't use the SPen much at all, but a quick test with SNote appears that everything still seems to work OK.
(But I did notice that the stock Samsung ROM (CMD2) does set these variables, which is unusual as these sysfs entries "shouldn't exist", but it seemed to (re)set them to default values. I wonder if this is used as part of a version check of some sort?)
Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack
JSale said:
Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack
Click to expand...
Click to collapse
Wow! Thanks for the testing and for the feedback on your results. This is quite interesting. I am not quite sure I can integrate this sort of thing into my app although it may be possible. The kernels for the Samsung devices I have looked at seem quite monolithic rather than modular. But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand. So perhaps. I would sure need help and direction. But it would be very cool indeed.
JSale said:
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked ROM?
Click to expand...
Click to collapse
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
whitedavidp said:
But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand.
Click to expand...
Click to collapse
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.
kcrudup said:
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.
Click to expand...
Click to collapse
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks
whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them?
Click to expand...
Click to collapse
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
Thanks very much once again!
whitedavidp said:
Thanks very much once again!
Click to expand...
Click to collapse
The app seems to work with this kernel :good:
kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
I really want to know what are the features of this kernel ... would i keep it or there are other ones that have this functionality right now?? OR could just this changes be added to the Stock kernel to only have Spen support .. as i dont want any OC or custom governers :good: :good:
whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks
Click to expand...
Click to collapse
May I ask you what application you are talking about?
@kcrudup Have you already decided to release your kernel in a separate thread or not?
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
Is this the source code for the Motoactv, including hardware drivers?
http://sourceforge.net/projects/motoactv.motorola/files/MOTOACTV-Americas/1.7.11/
Does this mean we may be able to get newer android versions?
gigaguy said:
Is this the source code for the Motoactv, including hardware drivers?
http://sourceforge.net/projects/motoactv.motorola/files/MOTOACTV-Americas/1.7.11/
Does this mean we may be able to get newer android versions?
Click to expand...
Click to collapse
I can't imagine getting any newer versions to run on this thing. The current version (ClearDroid rom) doesn't even run with multitasking.
shusain93 said:
I can't imagine getting any newer versions to run on this thing. The current version (ClearDroid rom) doesn't even run with multitasking.
Click to expand...
Click to collapse
What do you mean by that? I can multitask fine with mine.....granted, there is only so much you can do with 256MB of ram but it still works.
The actv is capable of doing anything the OG droid could do given the right files are made available......the OG droid could run jellybean (albeit not very well). From what I gather, kit kat has a smaller memory footprint so would perform better. I don't know if these files are the correct sources to get it working though. Sadly, most development has moved on so I'm not sure we will ever know even if it is possible.
EDIT: After looking at the code posted a little more deeply, it does appear this is indeed source code including drivers and kernel source.
Artimis said:
What do you mean by that? I can multitask fine with mine.....granted, there is only so much you can do with 256MB of ram but it still works.
The actv is capable of doing anything the OG droid could do given the right files are made available......the OG droid could run jellybean (albeit not very well). From what I gather, kit kat has a smaller memory footprint so would perform better. I don't know if these files are the correct sources to get it working though. Sadly, most development has moved on so I'm not sure we will ever know even if it is possible.
EDIT: After looking at the code posted a little more deeply, it does appear this is indeed source code including drivers and kernel source.
Click to expand...
Click to collapse
...Really? If someone did something with this it'd sure bring back my excitement for the Motoactv!
So our phone, is really good, we got cm 11 and cm 12 running, so why don't we have the more special roms? Like flyme os (http://www.flyme.cn/en/) or ubuntu touch? Sailfish os. Most of these, roms have their source released, so for people to pick it up, shouldn't be hard right?
Sailfish os - https://sailfishos.org/develop/hadk/
Ubuntu touch - https://wiki.ubuntu.com/Touch/Building
Flyme os - Well it's builded for the nexus 5, but aren't we able to port it? http://forum.xda-developers.com/google-nexus-5/development/official-flyme-nexus5-kk-4-4-flyme-3-8r-t2875908
And admins, please do not movie this topic, as it won't get as much focus.
bump!
I'd be interested too, what comes to mind is hardware limitations and lack of sources from LG to build on? I have for a couple of months and I still haven't wrapped my head in all the info, but I think we have some limitations as I mentioned above. Someone who's more informed can correct me tho
But aren't we able to port from nexus 5?
MidnightDevil said:
I'd be interested too, what comes to mind is hardware limitations and lack of sources from LG to build on? I have for a couple of months and I still haven't wrapped my head in all the info, but I think we have some limitations as I mentioned above. Someone who's more informed can correct me tho
Click to expand...
Click to collapse
But aren't we able to port from nexus 5?
theonlykamph said:
But aren't we able to port from nexus 5?
Click to expand...
Click to collapse
nexus 5 has a completely different chipset SD800 Nexus 5 Vs SD801 in the LG G3
sofir786 said:
nexus 5 has a completely different chipset SD800 Nexus 5 Vs SD801 in the LG G3
Click to expand...
Click to collapse
So let me get this straight, are we able to port any rom, from a phone as long as the cpu is 810 snapdragon?
theonlykamph said:
So let me get this straight, are we able to port any rom, from a phone as long as the cpu is 810 snapdragon?
Click to expand...
Click to collapse
The issue is that LG does not release the source code for LG G3, whereas the nexus 5 even though it is manufactured by LG, people have the sources for it. So developing all these different roms is not as easy as you think, we have only just got MIUI rom for this device and it is not even official. its not a SD810 btw.
sofir786 said:
The issue is that LG does not release the source code for LG G3, whereas the nexus 5 even though it is manufactured by LG, people have the sources for it. So developing all these different roms is not as easy as you think, we have only just got MIUI rom for this device and it is not even official. its not a SD810 btw.
Click to expand...
Click to collapse
I don't get it, can't we take the roms from another phone using our cpu, and just port it from there?
theonlykamph said:
I don't get it, can't we take the roms from another phone using our cpu, and just port it from there?
Click to expand...
Click to collapse
Lol you are not understanding, its not as simple as you think. Anyway i shall leave you with that.
sofir786 said:
Lol you are not understanding, its not as simple as you think. Anyway i shall leave you with that.
Click to expand...
Click to collapse
Okay, why so mean?
theonlykamph said:
Okay, why so mean?
Click to expand...
Click to collapse
Im not being mean at all, you're failing to understand that its not easy to just port roms, and its not even about porting roms, there has to be enough demand for it, devs need to have the device and not all devs do because they move to other devices, if it was an easy process then there would be loads of other roms, but the majority of roms are now Cyanogen and aosp based because thats the easiest way to as they have the sources for that.
sofir786 said:
Im not being mean at all, you're failing to understand that its not easy to just port roms, and its not even about porting roms, there has to be enough demand for it, devs need to have the device and not all devs do because they move to other devices, if it was an easy process then there would be loads of other roms, but the majority of roms are now Cyanogen and aosp based because thats the easiest way to as they have the sources for that.
Click to expand...
Click to collapse
I never ported a rom, but i saw some guide on porting a rom, where you would take something from the rom you want to port, and some from the base. So i thought it was like that! I'm so sorry, if i said anything mean to you Hope you have a great day :highfive:
Porting isn't the way you would want to work. For the best results you would need all sources and complete documentation of the hardware to be able to build a rom for a device from scratch.
Robin2 said:
Porting isn't the way you would want to work. For the best results you would need all sources and complete documentation of the hardware to be able to build a rom for a device from scratch.
Click to expand...
Click to collapse
But what if i just want to port a simple rom, is it just the cpu that has to be the same?
theonlykamph said:
But what if i just want to port a simple rom, is it just the cpu that has to be the same?
Click to expand...
Click to collapse
There is no "simple" ROM.
You can't just put another phone's ROM to G3, it doesn't work like that.
In PC world, you can install Linuxes and Windows operating systems mostly as you want, but in mobile, things are different.
So if there is no port for the custom ROMs then why not features like Download Booster from the Galaxy S5, this is a possibility maybe it is hard to do but give it a chance, just an idea that I like
TonzaTheChosenOne said:
There is no "simple" ROM.
You can't just put another phone's ROM to G3, it doesn't work like that.
In PC world, you can install Linuxes and Windows operating systems mostly as you want, but in mobile, things are different.
Click to expand...
Click to collapse
What i mean was, would i be able to follow some of those porting guides. Where you take a bit from the lg g3 rom, and then some from the rom you want to port?
theonlykamph said:
What i mean was, would i be able to follow some of those porting guides. Where you take a bit from the lg g3 rom, and then some from the rom you want to port?
Click to expand...
Click to collapse
As Robin2 put it ealier, you would need sources that aren't available.
The Rom porting procedures have been becoming more and more complex with time. Elements like drivers, framework, and so forth are much more complex comparing with Gingerbread. A rom by then used to be 300mb (stock), nowadays we got 1gb roms, much more "little things", overal, it's a lot harder and more complex. You can easily compare, there used to be more ports with gingerbread and ICS than with KK and L. It's a lot of work required to make things happen, even with the same chipset, there's still a lot left to do, specially when we're talking about lack of sources available to make a porting happen and much more complete.
Also, when we're talking about porting a stock rom from HTC to LG, gets worse. manunfactures put a lot of customization (not only GUI) into their firmwares, much more proprietary stuff, much more complexity comparing with a "simple" CM12. It's porting 200mb comparing with 1gb of custom elements. You get the picture. Unfortunatly it's harder than ever and so time consuming and not always with good results. Sources are literally a requirement these days and we don't have them (or don't have them all).