Hi! I was thinking in these days, studying (at elementary level) Unix o.s. for an exam, if it could be possible to merge the 4.4 version with our 4.1.
I mean, 4.1 has drivers, and other stuffs made by moto, and 4.4 has new framework and new kernel basically built for atom based x86 systems. So. If we adapt the new kernel at our phone (I've seen something similar was already done here in xda) and merge old drivers and stuffs with new framework, could it work?
[If I've just said ****, you are free to ignore me and delete the post]
There is some progress being made here. Take a look.
Porting over the framework might be possible. But the difference between the versions are more in the shared library's. We can't get art or sound working without building/modifying the library's. The framework is just what you see, it is the core of android that's has changed the most.
Sent from my GT-P5110 using XDA Premium HD app
Related
Hi, first of all I hope this is the right place for this if not please close/move and tell me the right place to ask.
I am planning to improve the CM-FM app for our N1s, it works but there is a lot of room for improvement (named stations, autosearch, overriding national limits...).
The problem is that I am working on a Windows machine and the FM app needs the modified CM framework classes to compile, it seems there is no option to compile the full CM distribution under Windows.
But it shouldn't be too difficult given the CM framework compiled to use it with android-SDK and eclipse to build just the app.
So I ask here if someone can provide me the compiled classes.
It would be great to have them published with the nightlies, but as I don't think there would be a lot of changes in this part probably I can work with an outdated version for some time.
Why don't you use a virtual machine with Linux for this?
Of course that's a last resource but surely there are people out there that can provide this classes from their last compilations without problems and maybe this can help other developers also.
You'd probably want to be able to compile CM anyway so just installing Ubuntu 64bit in Virtualbox will work fine and is free. Make sure to enable Hardware Virtualization in your BIOS if your CPU supports it.
I do want to compile CM just the radio app, otherwise I would have installed a linux.
Sent from my Nexus One using XDA App
frisco82 said:
I do want to compile CM just the radio app, otherwise I would have installed a linux.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Why so stubborn? It literally takes less than a few hours to install, download sources, and compile your classes. Instead, you'd rather post here, and sit in waiting for who-knows-how-long to get an answer?
Not flaming, just trying to follow your thought process...
Hi,
I have successfully set up FRG83 and Cyanogen repositories, I've compiled the whole ROM, and I've compiled specific apps (make Gallery3D, for example).
Now I'm trying to start working with Eclipse. I've installed it and imported Cyanogen repo into it as a project - worked fine. The problem is - what if I want to compile a single package from it, say, Calendar app only? What is the equivalent of "make Calendar" in Eclipse, and is there any?
Thanks.
Bump. I don't believe no developers pass around here..
Don't believe many people in here know as much as you... xD
I know you shouldn't post questions in the dev section, but it may be a better option?
Sent from my Nexus One using XDA App
Unfortunately there are still plenty of internal-only API calls in the AOSP system apps. This means that many of them will not compile using the SDK.
So the right way to work with them would be editing in Eclipse and building in command line, like I did. Oh well... Thanks
Im just curious. How does one go about creating their own working custom rom? I feel like it would take forever to get everything in precise working condition and have it available for the community.
Sent from my DROID3 using XDA App
What do u mean? There are already roms out such as Steel Droid and DarkDroid. I guess I am confused to this post.
Sent from my DROID3 using XDA App
It depends on who/how it's created.
A lot just take the stock ROM, delete some apps, make graphical changes to the framework and edit the build.prop file. They may add an app or two (free app) that they feel enhance the phone.
Others pull the source code from Google/Android down to a Linux based workstation and make edits to the source code. Adding their own source and what not to it, replacing images (icons) and some even add new features or functions not available by modding a stock ROM (pulling in their own libraries into the stock source build).
Currently there are ZERO "source" built ROMs for the Droid 3. All are working from the stock ROM and re-theme'ing it.
Hashcode though, is working on getting the CyanogenMod source tree to compile for the Droid 3 though this takes a lot of work trying to figure out what needs to be changed to make it compile and function on the Droid 3's hardware.
tcrews said:
It depends on who/how it's created.
A lot just take the stock ROM, delete some apps, make graphical changes to the framework and edit the build.prop file. They may add an app or two (free app) that they feel enhance the phone.
Others pull the source code from Google/Android down to a Linux based workstation and make edits to the source code. Adding their own source and what not to it, replacing images (icons) and some even add new features or functions not available by modding a stock ROM (pulling in their own libraries into the stock source build).
Currently there are ZERO "source" built ROMs for the Droid 3. All are working from the stock ROM and re-theme'ing it.
Hashcode though, is working on getting the CyanogenMod source tree to compile for the Droid 3 though this takes a lot of work trying to figure out what needs to be changed to make it compile and function on the Droid 3's hardware.
Click to expand...
Click to collapse
Thats interesting. Thats the kind of answer i was looking for. I was just curious. Thank you.
Sent from my DROID3 using XDA App
tcrews said:
It depends on who/how it's created.
A lot just take the stock ROM, delete some apps, make graphical changes to the framework and edit the build.prop file. They may add an app or two (free app) that they feel enhance the phone.
Others pull the source code from Google/Android down to a Linux based workstation and make edits to the source code. Adding their own source and what not to it, replacing images (icons) and some even add new features or functions not available by modding a stock ROM (pulling in their own libraries into the stock source build).
Currently there are ZERO "source" built ROMs for the Droid 3. All are working from the stock ROM and re-theme'ing it.
Hashcode though, is working on getting the CyanogenMod source tree to compile for the Droid 3 though this takes a lot of work trying to figure out what needs to be changed to make it compile and function on the Droid 3's hardware.
Click to expand...
Click to collapse
Speaking of CM74D3, I believe the last update was everything is working except GPS and Radio.
...those are two quite important things, lol.
@tcrews:
I have my laptop almost set up to pull the source code from Google and use that. However long it will take me to make something, however, remains to be seen.
Sent from my DROID3 using XDA App
I'm not a developer so please bare with me.
Why can't HTC Sense framework be packed into a ZIP or even APK? I realize the source code is likely under lock and key by HTC, but is that what is needed to make this work? Is it not possible to extract it from developer releases of their ROMs?
Computers can operate by being able to install different packages and frameworks to make certain software work, so why not for Android? The Xposed framework can be installed via APK (similarly to how one would install C++ updates for their PC).
It would be absolutely phenomenal, if taht is even a grand enough word to use if this would be possible. That way, HTC apps like Camera, ZOE, TV etc. would be compatible even on Google Play Edition or other AOSP ROMs.
I say this because after doing research I see that a lot of HTC Sense apps were ported to previous versions of Android GE (ICS for example) that still contained Sense framework files needed to make these apps work.
Could someone intelligible please enlighten me to this? I'd love to at least understand why this is, or is not feasible.
Elite83 said:
I'm not a developer so please bare with me.
Why can't HTC Sense framework be packed into a ZIP or even APK? I realize the source code is likely under lock and key by HTC, but is that what is needed to make this work? Is it not possible to extract it from developer releases of their ROMs?
Computers can operate by being able to install different packages and frameworks to make certain software work, so why not for Android? The Xposed framework can be installed via APK (similarly to how one would install C++ updates for their PC).
It would be absolutely phenomenal, if taht is even a grand enough word to use if this would be possible. That way, HTC apps like Camera, ZOE, TV etc. would be compatible even on Google Play Edition or other AOSP ROMs.
I say this because after doing research I see that a lot of HTC Sense apps were ported to previous versions of Android GE (ICS for example) that still contained Sense framework files needed to make these apps work.
Could someone intelligible please enlighten me to this? I'd love to at least understand why this is, or is not feasible.
Click to expand...
Click to collapse
Ok what you seem not to know is that the framework is the base file for the whole system. This is the file that the drivers and other low level code is set to use. HTC frameworks and AOSP or GE frameworks are very different. To make it work you would need to have HTC release all the driver code and then find a way to mix and match the frameworks to make it work. This would make it almost twice the size.
They will never make it into AOSP. As it goes against just what AOSP stands for.
zelendel said:
Ok what you seem not to know is that the framework is the base file for the whole system. This is the file that the drivers and other low level code is set to use. HTC frameworks and AOSP or GE frameworks are very different. To make it work you would need to have HTC release all the driver code and then find a way to mix and match the frameworks to make it work. This would make it almost twice the size.
They will never make it into AOSP. As it goes against just what AOSP stands for.
Click to expand...
Click to collapse
Ah, I see. Thanks for explaining that.
Another quick question though, if that is the case, why were users(devs?) able to port some HTC Sense apps to GPE roms on previous releases of Android like JB? Or has the entire GPE rom shrunken in size since then because of the obliteration of the lingering Sense files?
Hi, I'm a Korean Developer.
Recently Samsung has released android 5.0 lollipop for our devices.
But most of you may be ambarrased because the lollipop upgrade changed lots of things in system.
So I researched few days about it, and I've got several informations.
All of what I explain here is the result of my experiments.
In developers discussing forum, famous developers were discussing about "How we can mod lollipop system files".
Thanks to qwerty123258, Softdx's lollipop de-odexing tool has been known to here. But the problem is that how to re-odex the de-odexed apps,frameworks.
As our common sense, ART doesn't support de-odexed apks,jars so we have to re-odex them. But many of you may think we can't re-odex animore with the way we have used.
I agreed it at first.
So I've heard that de-odexed SecSettings,SystemUI apk with Softdx's tool don't work and have FCs. Thinking like this, we can think there is no solution. Especially, lots of custom ROM developers cannot make ROM without smali modding.
BTW, I saw that mods for nexus devices' lollipop are mostly de-odexed. But there is no problem.
Hold on, the ART definitely doesn't support de-odexed mods, but why mods for nexus doesn't have matter? You may think this doesn't make sense.
So I had doubt to this 'common thinks'.
And one day, I was putting Galaxy Note3's apps into my system that worked on KK.
FlashAnnotate app had FC, and Action memo popup also had FC. But the main app and widget of Action memo worked well.
Moreover, SuperSU that I used when rooting my S5 was also de-odexed app.
Isn't it strange to say "ART doesn't support de-odexed"? So I thought that Google didn't fully removed dalvik, they just inactivated it.
So I replaced the FlashAnnotate app with the one for Note4, and it worked well.
Then I put Note4's apps like S Note, Weather Widget, etc. As I expected, all of them worked with no FC!
Thus, it is wrong to say that the ART doesn't support de-odexed. It is the problem of that app.
What problem?
I asked to one of my friend, a Note3 mod-developer. He said that stock Note3 doesn't support ART natively.
This means that the developers of Note3's stock apps didn't care ART.
It has the same principle with the issue that the old version of stock apps like S health have FC on Galaxy S5 lollipop.
The structure of app's source code have to match with ART's structure.
In short, de-odexing have no relation with ART. FC issue is the compatibility issue of that app.
So the apps of after-KK-released-devices can be worked whether it is de-odexed or not.
Is this mean apps with FC cannot be used on lollipop? No. We can modify it to match with ART's structure. I mean, we can port it as API21(lollipop).
Let me pass to the other subject.
Most of you may think that re-odexing as the way we used, extracting dalvik-cache in the phone cannot be used and we must convert it as oat.
But, I re-odexed the main app of Action memo,what worked well even it was de-odexed, as the way we used.
It also works well while it is re-odexed.
Therefore, we can re-odex apps with the way we used.
BTW, as mentioned before, stock Settings and SysUI don't work when they're de-odexed and re-odexed.
It doesn't make sense according to the theories before. Then, what's the problem?
There is one that most of you may overlooked.
When you're de-odexing with Softdx's tool, generally most of you may think converting oat to dex is important and baksmaling/smaling process must be worked well.
But the problem was in baksmaling/smaling process.
When I was de-odexing stock settings app with Softdx's tool,
(look at the attached 1.png because I cannot insert image)
There were errors on smaling process. But I've never modded any smali of it.
When I looked the codes that made errors, not recognizing the '+'s on the pswitch code.
(look at the attached 2.png because I cannot insert image)
like this.
Many smali modders may know that there was no '+' on pswitch code when modding smali of KK or lower versions.
But after I remove all that '+', it can be compiled well but it has FC. Why? literally "It was modded".
It is reasonable to have FC because it was "modded", not compiled without modifications.
We can think of these two cases:
1. The structure of app's source code was entirely changed, so the last (bak)smali tool cannot recognize changed codes.
2. The structure of app's dex was entirely changed, so vanished parts are made when baksmaling with last tool.
We can conclude with these two cases.
After the release of (bak)smali tool that can completely baksmali/smali, we can do modifications.
I've heard that the developer of apktool is going to release new version for lollipop. So we have to wait a little bit.
Although we cannot do smali modding yet, we can put apks in system.
Why don't you put several apps in system and confirm what works or not?
Anyway, Thank you for reading my bad English...ahaha
If you have another opinion for my think, reply it.
Wow really much thnx for this!!