I'm new in Android ROM developing but I wonder why can't the "driver files" from stock Android 4.4.2 be placed on CM builds and make the NFC work. I made ROMs with modified apps or other customization so I don't know much about porting ROMs.
P.S.: English for bad sorry.
mihai.apostu98 said:
I'm new in Android ROM developing but I wonder why can't the "driver files" from stock Android 4.4.2 be placed on CM builds and make the NFC work. I made ROMs with modified apps or other customization so I don't know much about porting ROMs.
P.S.: English for bad sorry.
Click to expand...
Click to collapse
CM is based on complete different source codes. And a v different system than a kitkat. So there are two ways to get NFS active : a lollipop update by Samsung or drivers given by the company who made our device's NFC chip.
Related
So I want to install a custom rom but I am confused as to which I should use. I've read different roms and I've seen that they have different rom "bases" like cm 10.1, aokp, aosp, and PA(does it have a different rom base?). Just a question, what is the differences among them? Please help so I can decide which to flash.
Hmmm, good question, well most of the ROMs here are build off of official ROM source and thats what it means by base and the difference between them is almost everything from ui to features and stuff like that and to know which ROMs you like try flashing the the official ROMs like AOKP, CM, AOSP, and PA and then once you find the base you like then flash the other ROMs that are customized versions built from that ROM base
Sent Via Nexus 7
All of these ROMs are built from AOSP; that's Android Open Source Project. It's where Google officially releases the source code. All custom ROMs on this type of device will be built on AOSP. If a ROM says it has CM or AOKP base, that means they built it off the source code for that ROM (which is initially built off AOSP) and added their own tweaks or whatever.
Sent from my Nexus 7 using Tapatalk HD
The AOSP and cyanogen Roms which are available all of them have camera issues and other bugs. Why is it so?
Is it impossible to run AOSP on s4 i9500? If yes, then why so?
Is it because developers are slacking and just dont want to make a AOSP custom rom for s4 i9500 or there is something which limits developer from making AOSP avialable for s4 i9500. maybe samsung hasnt given tools or drivers to developers.
All the custom roms available for s4 i9500 . They all have written at the end of the thread that The rom is based on Stock firmware.
What is a firmware? Isnt it same as kernel?
Yeah I know I am total noob.
diper07 said:
The AOSP and cyanogen Roms which are available all of them have camera issues and other bugs. Why is it so?
Is it impossible to run AOSP on s4 i9500? If yes, then why so?
Is it because developers are slacking and just dont want to make a AOSP custom rom for s4 i9500 or there is something which limits developer from making AOSP avialable for s4 i9500. maybe samsung hasnt given tools or drivers to developers.
All the custom roms available for s4 i9500 . They all have written at the end of the thread that The rom is based on Stock firmware.
What is a firmware? Isnt it same as kernel?
Yeah I know I am total noob.
Click to expand...
Click to collapse
CM Based
Aokp - http://forum.xda-developers.com/showthread.php?t=2654985
Mokee - http://forum.xda-developers.com/showthread.php?t=2578676
Don't panic, I can see ROMs based on AOSP here: http://forum.xda-developers.com/galaxy-s4/i9500-develop
I have personally never seen a i9500 so I beleive they are just not that common or shipped to countries where there is a lack of devs. How about cooking your own? I've started to develop my own ROM which I'm using right now.
Firmware is a full system
The kernel also partly firmware
The kernel is the core of android
If no kernel will not boot
Note: sorry if i am wrong
I9500 has an exynos chipset which had been looked down by Samsung. This has been the case since the Galaxy S2. AOSP Roms exist for the i9500 but they won't be the most stable things you will try, so you are better off staying with the original software or a rom based on the original software.
Androiders96 said:
CM Based
Aokp - http://forum.xda-developers.com/showthread.php?t=2654985
Mokee - http://forum.xda-developers.com/showthread.php?t=2578676
Click to expand...
Click to collapse
as I said these roms have some serious bugs like random reboots bluetooth not working camera not working. These roms arnt good for a casual user.
DallaryPT said:
Don't panic, I can see ROMs based on AOSP here: http://forum.xda-developers.com/galaxy-s4/i9500-develop
I have personally never seen a i9500 so I beleive they are just not that common or shipped to countries where there is a lack of devs. How about cooking your own? I've started to develop my own ROM which I'm using right now.
Click to expand...
Click to collapse
Developing your own ROM is cool thing. That's what I will be doing after my next month exams.. I dont actually own a s4 i9500 but my cousin has it. I have xolo a500s. It's pretty looking device. I would like to port 4.4 kitkat AOSP rom on it.. :victory:
Androiders96 said:
Firmware is a full system
The kernel also partly firmware
The kernel is the core of android
If no kernel will not boot
Note: sorry if i am wrong
Click to expand...
Click to collapse
Thanks for replying. I think you are right. Firmware = rom + kernel.
ballsofsteel said:
I9500 has an exynos chipset which had been looked down by Samsung. This has been the case since the Galaxy S2. AOSP Roms exist for the i9500 but they won't be the most stable things you will try, so you are better off staying with the original software or a rom based on the original software.
Click to expand...
Click to collapse
Yeah that's it. Samsung doesn't share the full source code of it's exynos chip. half of the sourcecode is closed source. They just don't give the full source code to the developers. That's why developers fail to make custom kernels and roms.
But now I wonder why do samsung do this? Maybe they dont want other phone makers to know their unique performance tweaks which they have put in sourcecode.
Lesson learnt never buy Exynos powered device. Always try to get snapdragon powered device.
So, @neXus PRIME wants to make a locked bootloader-compatible ROM, aside from his wonderful AOSPA port. Now it's your choice, so choose the ROM you want carefully.
Huh one choice...
But one is not enough .-.
I know, but my hard disk space is not enough.
I have currently PA and aokp sources.
I am planning to replace aokp sources with the one you guys pick here. I can do a third too but then i will have to delete ccache space... But that is not good.
I'd like to see MIUI get updated to the latest version and see how that runs on our device because the MIUI interface itself looks pretty slick, and if possible a port of multirom would be a nice thing as well (if possible: don't know if our device is using fstab or rc)
noahvt said:
I'd like to see MIUI get updated to the latest version and see how that runs on our device because the MIUI interface itself looks pretty slick, and if possible a port of multirom would be a nice thing as well (if possible: don't know if our device is using fstab or rc)
Click to expand...
Click to collapse
I agree too
Like Paranoid Nexus, there is the chance of chosen rom to work with unlocked bootloader?
I can choice easier if I know which rom has what kind of features.
Actually MIUI seems like a good idea, plus it's a bit different when compared to the AOSP bunch.
Yeah MIUI would be cool, but if not i would love to see carbon or pacman on LBL.
@neXus PRIME
i appreciate your hard work buddy
instead of which rom you compile,i think we need advanced custom kernel like doomkernel...i'm currently using pacman 4.4.4 and none of cutom kernel present on forum does'nt works
Can we have avatar rom!
Avatar, Chameleon, AOSBam, Sonic.....wtf.... so many kangerzzz
But why is PURE AOSP winning out???
Don't know why but vanir being a ubl ROM is really fast and smooth, is it in the ROM or the optimisations by the dev??
In the feature code, ahe has mentioned many compiler optimisations, isbit because of them or the ROM????
I would have said Slimkat if bagyusz doesn't update it, but as of now i don't know if he will.
An update to the latest MIUI would be lovely, locked or unlocked BL is a matter of secondary importance for me
Apart from that Carbon, Vanir and PACman on a stock/stock-based kernel would also be nice
neXus PRIME said:
Avatar, Chameleon, AOSBam, Sonic.....wtf.... so many kangerzzz
But why is PURE AOSP winning out???
Click to expand...
Click to collapse
I think that some peoples want to have the android L version. Also they choosed Pure AOSP. This day, Google push the sdk of the android l version.
For android kitkat based, you can do MIUI Rom or if you want an AOSP, you can choose the AOKP.
The problem with android L is we'd have to check the LBL kernel modules we have work on it otherwise its another big job to update (if its even possible).
No L possible. End of story. Just vote the available choices
Well, when I was adding AOSP to the poll I didn't even think of Android L. Maybe I should have written it more precisely.
And yeah, there is a lot of work to do to make L work on LBL. The first thing that's coming to my head are Adreno drivers from 4.3(we are using them in KitKat, so it's not clean and fully working by any means). The second thing is power saving mode in L: we don't know if that's a kernel or OS feature... And there are many things that may result in a complete incompatibility between our kernel and Android L, and changing ramdisks won't help in that case.
Aren't the sources for L coming out in September? Why even talk about it now, wait till the Cyanogen team start to push the first nightlies, then we can put Android 5.0 in the conversation
I recently rooted my phone. I wanted to install a custom rom. My friend installed cleankat v2.6 but i wanted to go for something better. As expected none of the nicer ones like cyanogenmod or paranoid android or aokp roms were available. I managed to install htc sense rom . it is working but has lots of bugs. As soon as i make a call it crashes and screen goes blank. Nothing opens .it doesnt even swit h off and i have to remove the battery every time i make a call and reboot it.
Secondly many apps including settings crash for no reason.
Plz. Help coz i really want dat rom working fine
[email protected] said:
I recently rooted my phone. I wanted to install a custom rom. My friend installed cleankat v2.6 but i wanted to go for something better. As expected none of the nicer ones like cyanogenmod or paranoid android or aokp roms were available. I managed to install htc sense rom . it is working but has lots of bugs. As soon as i make a call it crashes and screen goes blank. Nothing opens .it doesnt even swit h off and i have to remove the battery every time i make a call and reboot it.
Secondly many apps including settings crash for no reason.
Plz. Help coz i really want dat rom working fine
Click to expand...
Click to collapse
Hi Murali,
The nature of mobile development is such as you have mentioned above. It doesn't work like windows or linux etc where you can install a generic OS on any system configuration by any manufacturer. The firmware has to be specifically built for your device. It takes great skill to port inter-device especially inter-manufacturer ROMs, so the fact that you actually have a bootable and semi functional SENSE ROM for a non HTC device itself is a big achievement. But it will never function on your Micromax phone like it does on an actual HTC phone. There are too many dependencies to counter. Also, there is a lot of closed source code that is not freely available to developers, especially with overlays like Sense and TouchWiz.
I would suggest you look for a good Custom ROM built on your phone's official firmware or wait for support from CyanogenMod, PA, Slim or such series to offer support to your device.
Sorry for the bad news, but I hope it helps.
what ab
Will flashing a custom kernel help or change the compatibility of the rom?
[email protected] said:
Will flashing a custom kernel help or change the compatibility of the rom?
Click to expand...
Click to collapse
It might. Then again, it might not. Changing kernels can make a huge difference in performance, both in a good and a bad way. There are too many variables to contend with, and without a strong active community behind your device, any answer I give you will be just guesswork and not based on facts. You can always try out a couple of compatible kernels and test out the difference.
Sorry I can't be of more help.
If we want to run a rom he can't (directly) we have to wait untill someone made it specifically for us. Thats fine i got it very device have its own kernel and rom integration. But if a person is using the same exact tree as official one do then why it is difficult to run stock apps directly w/o proting them.
Is it because of some legacy or copyright problem. One can build a rom on its own w/o having a team(like los, rr, paranoid).
Why porting is necessary? I would like to know that too
Sent from my Moto G4 Plus using Tapatalk
Cause you dont have updates
I am not a code/programme guy,
But what i have learned is, these different ROMs (Stock, AOSP based, Lineage based) have 0 (zero) interchangeability to their stock apps (except common apps). These may be because they use different codes?
For example, lineageSU addon will work only on lineagebased ROMs. Moto apps will work only on stock.
This looks like this apps are coded in way that it run only for specific ROM/device,
If you want such apps you need to modify it..
About ROM,
There are 4 sources/trees, 1)vendor 2) device 3)ROM 4)kernel.
Vendor, kernel, device tree can be used same for any ROM,
but ROM source is different for each ROM, which defines what is base of that ROM. You cannot build stock based ROM, you can only debloat,deodex, and modify stock ROM...
So, on different ROM, you need to modify apps to run...
@DgnrtnX I recommend to read that article about blob's so you get a better understanding why there's so much effort needed to "port" apps for example: https://www.xda-developers.com/came...opers-make-hardware-work-without-source-code/