Related
Hey, new to the forums, recently purchased a GSM Hero.
I have done some development for free software (think freedom, not price) projects, and have become accustomed to git repositories and structured development.
Upon entering the world of custom Android ROMs (at least Hero ROMs) I have been sorely disappointed with the development practices going on, releases on file sharing sites and the like.
On top of this, none of the ROMs available suit my needs.
This is all fine, as I'm not developing those ROMs.
I have decided that I need to start working on my own custom ROM, however guides and documentation regarding this process are in short supply.
It would be much appreciated if someone could link me to some guides to starting my own custom ROM.
I intend it to be a light vanilla ROM, with none of the bloat that seems to perpetuate other ROMs, I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
naivemonarch said:
I'm aware other such ROMs do exist, however none of them support all features, and even those that claim to do so, often require me to FC
Click to expand...
Click to collapse
Have you tried this one ? >[2.1] aychteesees-vanilla-cupcake< NOT the [3.0.1]verison ..this is still @dev
http://android.modaco.com/content/h...96/3-0-1-aychteesees-vanilla-cupcake-rom-gsm/
Give it a try [2.1] ! and tell us how it went ...
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
I'm downloading 3.0.1 as we speak, however I'd still like some resources on making my own ROM.
I'm interested on this documentation too....thanks
naivemonarch said:
Yeah I tried that one, it claims to have full functionality, however I frequently had to FC various applications.
Click to expand...
Click to collapse
That's weird , I have used almost everything ( apps ) with that ROM [2.1] ... and never get FC's
Did you flashed from Zero .. I mean with all he possible wiping . inlcuding SD ext partition wipe
???
That is a MUST ..!
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
This leads me to another question: all these custom ROMs that we see available for download -- are they free/open source? Like, do they have source code available? I certainly don't think they do, but if they don't, then aren't they violating the terms of the GPL by not providing source code?
Click to expand...
Click to collapse
There's Paul's (modaco) online kitchen, but if you want to compile by yourself, there's a plethora of gits on github (cyanogen, lokx, kiall to mention just a few).
Good question. Yeah it would be nice if there was a 'Cooking Class' thread on this forum like in some of the other forums. There is a decent tutorial however at HTCpedia.com under the HTC Hero ROM Development section, it's in the stickies there. However, I still have questions and that forum is not visited as much as xda.
Link to cooking thread:
http://htcpedia.com/forum/showthread.php?t=1404
FunkTrooper said:
Before this gets too off-topic, I too would like to concur with what OP is saying. I'd love some info on where to begin with custom ROMs, and I think it would be great if we could create a community repo for code for a custom ROM.
Click to expand...
Click to collapse
As a start, I would read that thread I just linked above. Once you can dump the contents inside the system.img and then combine it with the boot.img to build an update.zip, then you are already halfway there - that's actually fairly easy. But knowing how to add custom kernels to the update.zip, making the custom ROM rooted, etc. are all stuff that I'm still working on. There's supposed to be a lot of info in the Dream/Magic forums, so I'll keep reading.
Android is still fairly new and very few people know how to use Linux, thus there's less support and less interest in wanting to cook for one's own Android device.
BTW, that thread I linked above is also found here.. Doh!
http://forum.xda-developers.com/showthread.php?t=551711
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
naivemonarch said:
Thanks for the link, a good read.
Anyone know what the process is for using a custom kernel? There are a few things I'l like to enable that aren't in the HTC kernel (like FUSE).
Click to expand...
Click to collapse
If I eventually manage to find out I will post it here. My most important concern is making a rooted ROM from those shipped ROMs, as some people have been doing here.
Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!
FunkTrooper said:
Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!
Click to expand...
Click to collapse
1) The whole sources for everything are there
http://github.com/ninpo
2) You can import the sources to eclipse, but I think you will need to build the entire tree, as opposed to just what you change
3) Apktool lets you do smali and resource edits on an APK. Without knowing what you aim to do, it's hard to guide you specifically.
Most apps are based on the sources provided by google. I assume you are talking about Froyo Hero ROMs (i.e. FroydVillain), which apps are generally built from the source of CyanogenMod. Specifically for FroydVillain, if you look around ninpo github you will see some packages with some changes to their code, although it does seem that many of the changes in recent releases are not there. I have actually PMed ninpo about this and hopefully this is only a technicality.... I assume that the other packages and apps (most of them) he just compiled off the CM sources without changes.
In any case, if you compile an app either from the CM source or from google's original sources, it should work just to copy the apk file - just make sure you use an appropriate ROM (i.e. Froyo ROM if you built it from Froyo sources). The reason to want the CM sources, is that if they have incorporated further fixes (over the google sources) you may want them.
Finally, some more practical advice: I would start with the google sources: http://source.android.com/source/index.html since I have found these instructions and explanations easier to begin with - it should be quite straight forward to build these sources on a linux machine (or VM).
Then you can also try to tackle the cyanogen source: http://wiki.cyanogenmod.com/index.php?title=Building_from_source currently missing instructions on how to build for hero. But if you only want to copy apks out of it, you can just build a generic build (like in the google souce).
If you have specific problems, ask and I'll try to help you.
Good luck.
pulser_g2 said:
1) The whole sources for everything are there
http://github.com/ninpo
Click to expand...
Click to collapse
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .
Thanks for the advice I love this forum!
What I'm trying to do, in case you're wondering, ultimately, is to modify the built-in messaging application to give the user the option of sending a message by the normal method, or by using their provider's free webtext service, something that all the carriers seem to offer here in Ireland.
So, for example, you'd press the Send button, and you'd be able to select one of those methods. (of course, you'd have to have a data connection for the webtext). There's also be an interface for entering your login credentials for your carrier's website.
I'm doing this party because it would be very useful. I also feel that it would give me a good introduction to how you'd go about modifying Android. I mean, from a programming point of view, it shouldn't be *too* hard to do. I already have a simple standalone app that I made which can send a text message via an Irish carrier's webtext service. But it's all good experience to try to modify other people big codebases.
I have a good bit of experience with web application development, but my experience with other programming is a little more limited. I usually use PHP, where there's none of this compiling nonsense. You just write scripts and off they go!
So I'm gonna go off and see if I can set up an environment where I can build.. the OS, I guess.
If I was to take the vanilla official Google sources, would they work on my phone? Or would I have to use an official Google developer phone... or the emulator? Or maybe if I stopped writing here and investigated those links you've provided, I'd know that by know.
Brb, investigating
Yeh investigating and just trying to do it is usually the best way
To clarify what I was trying to say above: All the java code is obvious very portable - one of the big advantages of java. In the case of android it is compiled to an .apk file and this file should be, at the very least, portable to all android "devices" running this android version. So the apk you build (for example from the vanilla 2.2 sources) should work on the emulator (good for initial debugging) and any 2.2 ROMs.
erasmux said:
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .
Click to expand...
Click to collapse
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.
Hacre said:
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.
Click to expand...
Click to collapse
Thanks Ninpo
[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol
******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528
ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
updated approaches and new tools have been added
spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?
ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu
Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.
spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.
spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Goal and tools updated*
spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?
lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash
I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
And i'm sick of such useless posts. They will release it when they will release it. Get a life.
Why would they publish the source for a test RUU? 1.29 OK but not 2.05 yet
zvieratko said:
I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.
Click to expand...
Click to collapse
you forgot one main thing
2.05 is unreleased and leaked
And now no more leaked test releases lol.
Well done!!! Demand source codes for versions that aren't even released yet.
Lmao what is going on here
Sent from eXoDiZeD rom
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.
zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.
Click to expand...
Click to collapse
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol
hamdir said:
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol
Click to expand...
Click to collapse
That might be true. But AFAIK the 2.05 RUU was provided to some public testers as well.
I just opted to demand 2.05 as well in case it takes them a month to respond and it will be released by then, it did no harm in any case.
Also, we wouldn't have to have this debate if the development was actually transparent (that means - HTC working with community, not just pushing uncompilable sources for their old kernels). But I guess most managers can't grasp that concept without the proper buzzwords.
Sorry, I'm pissed at many more things than just HTC right now, but I directed my anger here
zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!)....
Click to expand...
Click to collapse
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.
AdamLange said:
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.
Click to expand...
Click to collapse
You know that kernel is GPL and what that means, right? Or are you just trolling? HTC is obliged to provide source code - it's not a goodwill gesture, and they consistently fail to do that.
Or are you talking just about 2.05? In that case, the first tester outside HTC should get the source code and would be free to release it to us - closed beta or not.
Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.
AdamLange said:
Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.
Click to expand...
Click to collapse
Yes, but they don't even post the sources without blobs...
sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Pmsl
TRULY COCKED ROMS
pro tip, if you don't act like a self-entitled brat when asking for something which they are required todo you are more likely to get an informed helpful response.
if that really is the email that you sent I wouldn't be surprised if it was just moved to the email bin
AdamLange said:
And i'm sick of such useless posts. They will release it when they will release it. Get a life.
Click to expand...
Click to collapse
+1:good:
Patrick Volkerdings: Its finished if its finished
sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Frankly ,they can have x3 more custom rom`s but we have one who is better then all SIII ROM`s together , we are so lucky and really need to be proud with our original developers like Venom Team , so S3 performance without ROM like our ViperX is in vain.
Don`t worry be happy! :victory:
Thread now closed. This thread has become off topic. I have had to remove a couple of posts that had bad language. Remember people to follow XDA rules when posting.
Moderators Note about MoKee. These ROMs in the past were known for distributing adware/malware. As they claim to be "Open Source" now, you should still be cautious about flashing MoKee ROMs. Currently this ROM is under review by Moderation Staff.
Android 4.4 Kitkat for Defy and Defy+
This is the latest Mokee ROM for our very own and never dying cell,Motorola Defy/Defy plus(Aka.jordan/jordanplus) based on the latest android OS Kitkat 4.4.
About MoKee OpenSource:
MoKee OpenSource is based on Google AOSP and CyanogenMod Android source development of a branch,
but also the country's first complete open-source Android project, users and developers around the home.
Google open source projects follow the rapid escalation, and for the user habits, improvements and enhancements.
Magic Fun Forum December 12, 2012 launch of the project, is committed to making this form of localization of open source CyanogenMod ROM.
Open source project, any interested technical experts who can participate in the development, its contribution to the force!
Project Address: http://www.mfunz.com
Click to expand...
Click to collapse
Mfunz/Mokee os Official page http://
www.mfunz.com/
Developers http://www.mfunz.com/contributors/
Forum: http://bbs.mfunz.com
Tutorial: http://bbs.mfunz.com/
thread-653126-1-1.html
Statistics: http://stats.mfunz.com
audit: http://review . mfunz.com
Github: https://github.com/MoKee
code tracking: http://issues.mfunz.com/
code tracking - Mobile: http://issues.mfunz.com/
mobi
Open source project, any interested technical
experts who can participate in the development of
its contribution to the force!
Project Address: http://www.mfunz.com
Update recovery first then flash this:
Download :http://pan.baidu.com/s/17YFiu
Gapps:?
Here is the link from the original post:
http://bbs.mfunz.com/thread-920983-1-1.html
Change Log :http://changelog.mfunz.com/
Screenshots :
As I can see you've post the 14.12 version and not the last 16.12 version which contains many bugs repaired. Can you post the last one? THX.
Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/
niksy+ said:
Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/
Click to expand...
Click to collapse
My solution is very simple Root Explorer and delete all parts of the MoKee from /system/app
niksy+ said:
Guys, but why are you still using Mokee, aren't they including malware in every ROM now? :/
Click to expand...
Click to collapse
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).
deffyplus said:
My solution is very simple Root Explorer and delete all parts of the MoKee from /system/app
Click to expand...
Click to collapse
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).
Click to expand...
Click to collapse
Exactly ! )
And i also use it as i dont get battery drops like in cm10.2
pgreed said:
As I can see you've post the 14.12 version and not the last 16.12 version which contains many bugs repaired. Can you post the last one? THX.
Click to expand...
Click to collapse
On the official site i am getting 14/12 build only....if u get some link do send me,i'll add it to the post
pgreed said:
Those Chinese apps is not exactly malware. Because is not useful for me I've uninstalled it with Titanium and recover some ROM. Also I replace the Mokee launcher and keyboard and make a very reliable and stable OS ( 4950 pts under Antutu 4.1.4).
Click to expand...
Click to collapse
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad?
And then when people caught on to it they also modified the keyboard app too... but nah... can't be that bad, since they are actually fixing many bugs that aren't being taken cared of by serious developers that contribute directly to XDA, right? Oh wait, their change log doesn't really reflect anything different than what's already being taken care of by other developers who are actually compiling and programming for our Defy...
As a tip, you can and should delete those apps before flashing (with 7zip), that way they aren't ever run on your phone; once you flash the first thing that will start up will be the keyboard.
Antiga Prime said:
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad?
And then when people caught on to it they also modified the keyboard app too... but nah... can't be that bad, since they are actually fixing many bugs that aren't being taken cared of by serious developers that contribute directly to XDA, right? Oh wait, their change log doesn't really reflect anything different than what's already being taken care of by other developers who are actually compiling and programming for our Defy...
As a tip, you can and should delete those apps before flashing (with 7zip), that way they aren't ever run on your phone; once you flash the first thing that will start up will be the keyboard.
Click to expand...
Click to collapse
that it is also possible
Antiga Prime said:
And how is it that it's "not exactly malware"? Is it just partially malware? Almost malware? Maybe malware? Or is a "variant of Android/TrojanDownloader.Adload.B trojan" really just not that bad? ... be the keyboard.
Click to expand...
Click to collapse
maybe the correct term is adware? For the rest: I found that ROM to be the most stable, battery efficient and with all the settings I need. 'till now the rest of 4.3 custom ROMs do not comply with the above needs and the 4.4.x is not enough mature. The only problem with Mokee 4.3 is that SistemUI slowly growing which suffocate the RAM and need periodical reboot -but that appear to be common to 4.3.x . Those grow seems to be closely related to apps installation and update.
---------- Post added at 08:09 PM ---------- Previous post was at 08:00 PM ----------
abhinavvaidya90 said:
On the official site i am getting 14/12 build only....if u get some link do send me,i'll add it to the post
Click to expand...
Click to collapse
Hm .. the 16.12 version seems not to be public yet!
pgreed said:
maybe the correct term is adware? For the rest: I found that ROM to be the most stable, battery efficient and with all the settings I need. 'till now the rest of 4.3 custom ROMs do not comply with the above needs and the 4.4.x is not enough mature. The only problem with Mokee 4.3 is that SistemUI slowly growing which suffocate the RAM and need periodical reboot -but that appear to be common to 4.3.x . Those grow seems to be closely related to apps installation and update.
Click to expand...
Click to collapse
Hardly the point. First of all, the fact that they have to hide it in an app most people will need to start up the ROM is shady at best. Second of all, regardless of how AV companies label the malicious software they find, a trojan downloader is essentially a backdoor for the app developer to open it and to deliver a payload that can behave differently than just "adware", without the user's consent or knowledge. That fact alone should make people think twice before installing/using this ROM, especially once people are aware that the developer's intentions are not necessarily intentions that promote the improvement and development of Android.
People can choose what they want, just my two cents on why we are tolerating malware, adware, trojans, or whatever you want to call it. There are a lot of people who also frequent these forums who won't know how to delete the malicious apps before flashing, regardless of whether they should be able to or not.
It's different when you have to mod things to your liking or to improve functionality, but hidden and persistent malware/adware placed by the developers themselves...?
We shouldn't have to tolerate that...
Antiga Prime said:
Hardly the point. First of all, the fact that they have to hide it in an app most people will need to start up the ROM is shady at best. Second of all, regardless of how AV companies label the malicious software they find, a trojan downloader is essentially a backdoor for the app developer to open it and to deliver a payload that can behave differently than just "adware", without the user's consent or knowledge. That fact alone should make people think twice before installing/using this ROM, especially once people are aware that the developer's intentions are not necessarily intentions that promote the improvement and development of Android.
People can choose what they want, just my two cents on why we are tolerating malware, adware, trojans, or whatever you want to call it. There are a lot of people who also frequent these forums who won't know how to delete the malicious apps before flashing, regardless of whether they should be able to or not.
It's different when you have to mod things to your liking or to improve functionality, but hidden and persistent malware/adware placed by the developers themselves...?
We shouldn't have to tolerate that...
Click to expand...
Click to collapse
Completely agree with you. Personally I think this ROM should be banned from XDA, where piracy and even promoting your paid themes isn't allowed. For me it is unimaginable that a trojanned ROM can be posted. discussions about how easy it is to remove don't matter, like you said. Hence I have reported to the mods.
@ others: Yes people can choose what they want, like antiga said, but on XDA the choice of installing trojans shouldn't even exist. There are shadier websites one can visit to get their trojan fixes.
Thread currently closed
Ok, 2 things.
1) Thread moved to General, as it's just links to the MoKee site, as it appears the OP is not an official maintainer, and just posted links. As such it does not qualify as development.
2) Thread is currently closed pending investigation of current MoKee practices.
In the past MoKee had been known to included adware in their apps. Did they include Malware? Depends who you talk to. However, MoKee was discouraged at XDA, along with MIUI ROMs which also operate under a similar principle.
However, MoKee claims to be "Open Source" and their github seems to reflect that.
It is advisable however, to remove any suspicious apk's just to be safe until a disposition is made. And considering it's a Chinese ROM with a past reputation, might want to change keyboard apk's as well
Thread closed for the time being.
MD