Hi everyone,
I apologize if if this is not the appropriate place to post this info, but I thought it would be of interest to some people here. You may have seen stories in the news recently about the privacy-monitoring extension for Android called TaintDroid that was developed by researchers at Penn State, Intel Labs, and Duke University. An excellent summary can be found on Ars Technica.
The reason I'm posting to this forum is that we are proud to have made our source code available last night. If you want to play around with the code, you can find it at the TaintDroid website (search "taintdroid appanalysis"). Along with links to the source code, you will find instructions for getting the code up and running on a Nexus One. We have also set up a Google Group for users who want to discuss anything related to the project.
Our only caveats are that we are merely researchers so 1) you use the code at your own risk, and 2) we do not have the resources to offer proper support. We hope that by releasing the code to the public a self-sustaining community of interested users will form.
We hope that you find our code interesting and useful. Happy hacking!
-landon
Thanks for releasing the code. Look forward to using it on an incredible rom soon.
http://appanalysis.org/tdro1d.html
I'm assuming that's the link. Couple of questions.
1.I see it's on 2.1 rom, does it work with 2.2? Especially as it uses the 2.6.32 kernel.
2.Since the Desire is basically a Nexus One with sense, has it been tested on that platform or with sense?
Thanks for releasing the source and instructions!
This is what Android needs, as Google is not taking good care of the privacy of it's users.
It's impossible to install apps now, because most of them want really wide rights, but you have no idea what they do with those rights.
TaintDroid at least gives a possibility to peek into what is being leaked.
Soon some of the app makers will start to encrypt their calls to try and and mask what they are leaking. If/when this happens, it should be a warning sign to users about that particular app.
This thread is for the discussion related to the NEC Renesas EMMA Mobile EV2 BSP/SDK.
For public information or documentations about the chip itself, please visit
http://www2.renesas.com/mobile/en/emma_mobile/em_ev.html#pageLink04
Why I am posting here?
This thread was originally started at slatedroid.com by one member who had drawn my attention there.
The reason I was interested was because there was a community of Rena3/Opad users there who are having an active discussion of things related to Android tablets based on NEC Renesas EMMA Mobile EV2 chip. The community there are interested to port Cyanogenmod to Rena3/Opad or develop a custom ROM for the Rena3/Opad tablet.
Part of reason they want a custom ROM was because Rena3's firmware is badly implemented. Users have reported many bugs on it and the chip's performance is not fully optimized to utilize its two cpu either.
Their problem is that the source code of the NEC Renesas EMMA Mobile EV2 chip is not publically available, so they can't really do anything other than simple modifications.
However, I have previously stumbled upon the NEC Renesas EMMA Mobile EV2 BSP/SDK somewhere on the internet. With the help of interested developer, in slatedroid's SDK thread, I have confirmed that the BSP/SDK I have is the NEC Renesas EMMA Mobile EV2 BSP/SDK that they need.
I was planning to make it available on slatedroid.com but something I posted offended the moderators there..... And I was banned immediately without warning or recourse.
The slatedroid member who had originally invited me to slatedroid was also banned when he was trying to help me to get my account re-instated.
Hence, I have no choice but to find an alternative forum to continue the SDK thread from slatedroid.com
This forum seems to be a good choice, that's why I am posting here now.
You can visit the original thread here
http://www.slatedroid.com/topic/21660-sdk-possibly-on-the-way/
I have attempted to post this thread on androidtablets.net but this thread was deleted within 24 hours of posting (My account with androidtablets.net is not banned and still usable though....).
It was lucky that Google have a cache of this thread, so I don't have to retype the whole thing again....
Note: the same thread is posted at
http://tabletrepublic.com/forum/cor...droid-devices-incl-tablets-custom-rom-90.html
http://androidforums.com/custom-rom...-android-devices-incl-tablets-custom-rom.html
I believe there are ROM developers here who may also be interested in this NEC Renesas EMMA Mobile EV2 BSP/SDK.
If not, I hope those member from Slatedroid.com would find their way here because I cannot make any post or even read slatedroid after I was banned.
With the help of fourgate from slatedroid, we have already uploaded the entire SDK/BSP on some file hosting web site.
About the BSP/SDK
So far, what we know is that the NEC Renesas EMMA Mobile EV2 BSP/SDK I have obtained is dated around april 2011. There are a number of known bugs inside the BSP/SDK which have been fixed by some vendors by now (September 2011), e.g. a lot of bugs were fixed in our Gen-E tablet by our supplier and we are now (September 2011) using a firmware is now running a kernel which is dated in August 2011.
In order to port the latest version of Cyanogenmod or AOSP, i.e. Android 2.3 or later to NEC Renesas EMMA Mobile EV2 based tablet, you can expect that some work is required to update the kernel and fixed bugs that have already been fixed before...
In addition, we noticed that the BSP/SDK I have obtained is not complete but do contains the most important parts that you need. Yes, kernal source is there....
To get you started, this is the release notes of the BSP/SDK.
http://www.sendspace.com/file/9d6f8e
Calling for ROM developers
If you are a ROM developer, capable of porting Cyanogenmod or AOSP to NEC Renesas EMMA Mobile EV2 based tablet, interested to work on this and want access to the source codes, please reply on this thread with the following information
1) State who you are
2) What do you intend to do with the file
2) What Renesas EMMA Mobile EV2 based device you currently own, if any. Or state none if you don't have one.
Once I see your post, I will sent u the download link via PM (please do NOT post the link I provide pubically but you are free to create a mirror copy of it elsewhere and post the link here.)
Why do I request these information?
So everyone knows who is trying to work on this because at present (17th October), because there are too few developers working on this and we would like to be able to contact them to seek update or have them available to help out other developers who are also working on this. I only know one developer, who found me through these threads, is actively working on this
In order to keep the BSP/SDK publically available, after you have downloaded the BSP/SDK, I would like to ask you to help us upload, host the file somewhere else and post a reply here to share the download link. Then, I will update the download link on this post here.
Public repository
To help with collaboration, I think we would need a repository to store/merge the code from different developers.
Most opinions received so far are to host these files at github (Or you have a better suggestion where we can put the modified source code?)
I am not a developer and I can't help on this. So, I would need a volunteer to upload and manage this......(anyone?)
nOISEVAULT said:
You can look here for the code.
I organized it in three repositories based around the tar.gz files in the SDK.
If someone wants to reorganize that's fine by me.
https://github.com/cAPSLOCK7
Click to expand...
Click to collapse
Useful informations related to this
For those ROM developers who do NOT have a NEC Renesas EMMA Mobile EV2 based tablet, if you have proven yourself that you are genuinely making contributions towards Cyanogenmod or ASOP build for NEC Renesas EMMA Mobile EV2 based tablet. We are willing to provide you with our Gen-E tablet at a discounted price. Please PM me on this matter after you made some contribution here.
(reserved for additional information)
You can use github for source code management
cdesai said:
You can use github for source code management
Click to expand...
Click to collapse
Another developer have mentioned that before but the most important part is still trying to have ROM developers interested and then they are put the source code up on github.
Being a non-programmer, I can't do these....
Firstly, I am interested in doing rom development for the rena3 which I own (typing this very message on it). I am new to android rom development but not new to android or development.
But I have two questions.
1. Why are you getting banned from forums? At slatedroid the admin said you were only conditionally willing to share the SDK.
2. Why not upload the SDK to github and let us start working on roms for the device.
Something is fishy about this whole thing to say the least.
Managing Director
Portable Electronics Ltd // Seller of Gen-E Android devices
Click to expand...
Click to collapse
nOISEVAULT, this is the answer on both of your questions
He's getting banned because moderators think he's promoting his products.
He cannot use github or smth else 'cause he's not a technical user, he's mostly like "people manager" trying to get his team connected to XDA developers.
So, ericwong, what do we need to get started? Can you upload an archive with current version to a file hosting so we can use it to set up a developer repository?
For example, you can use multiupload.com — it uploads your file to a number of free hosting services, so you can be 99,99% sure that the file will be available for about a month.
Oh, I see you don't know how to use github.
Then why not just upload the SDK to a filesharing service, and let the devs who will be interested take it and upload the code to github etc.
I don't think you will interest bees by just TELLING them you have a field of clover. You need to show them.
ericwong said:
For those ROM developers who do NOT have a NEC Renesas EMMA Mobile EV2 based tablet, if you have proven yourself that you are genuinely making contributions towards Cyanogenmod or ASOP build for NEC Renesas EMMA Mobile EV2 based tablet. We are willing to provide you with our Gen-E tablet at a discounted price. Please PM me on this matter after you made some contribution here.
Click to expand...
Click to collapse
Managing Director
Portable Electronics Ltd // Seller of Gen-E Android devices
Click to expand...
Click to collapse
ericwong, please consider that even this thread looks suspicious. We have no source code yet, but we have an offer to buy a «Gen-E tablet at a discounted price». Not a big surprise you were banned on some forums already. This is not the way the things get done.
Zombieff said:
So, ericwong, what do we need to get started? Can you upload an archive with current version to a file hosting so we can use it to set up a developer repository?
For example, you can use multiupload.com — it uploads your file to a number of free hosting services, so you can be 99,99% sure that the file will be available for about a month.
Click to expand...
Click to collapse
One of the interested developer, fourgate from slatedroid have helped me to upload the bulk of the files to a file hosting. However, I have not heard from him since.
I have updated my post with more information, please read it.
I am be more than happy to provide you with the file if you are willing to help setop the developer repository.
Zombieff said:
ericwong, please consider that even this thread looks suspicious. We have no source code yet, but we have an offer to buy a «Gen-E tablet at a discounted price». Not a big surprise you were banned on some forums already. This is not the way the things get done.
Click to expand...
Click to collapse
I am ONLY trying to help interested developer purchase a unit if they don't have a unit to work on. There is no obligation to purchase. This is NOT an advertisement to sell my products.
I can certainly ask the only active developer to post here to update his progress so far here to proof to you that this is not a hoax.
I can also provide you with the actual source if you are a ROM developer interested to help on this work. (please read my earlier post again, I have updated it.)
As I said. I am interested in trying to work on developing roms for this device.
If you will give us a link to the SDK we can start doing that. Where is the link?
Well, i agree, this is not the way to get things done, put the code there, without conditions and people will join, put just a load of words conditioning resources, and you'll probably get banned again, i'm not a rom developer, but a programmer, i'll start reading about rom deving when i get my device (2 weaks or so), which has an ev2 (is probably the same, just put together/rebranded by a diferent chinese company).
There is quite some documentation available (with no conditions from renesas), this might be lower level than the required level to dev a rom, but probably, scratching a bit more, there is a chance to find more, as for specific components (such as wifi, 3g modules, gps modules etc...) they have to compile with the suported devices by this SoC i can't post the link cuz this will be my 4th post, but i can tell you that what i found is this:
EMMA Mobile EV Series Pamphlet (probably worthless)
EMMA Mobile EV2 Datasheet
EMMA Mobile EV/EM User's Manual (this might be the most usefull)
On the renesas webpage is also the block diagram for the SoC, still have to do a crapload of reading b4 i can even pretend to know what needs to be done to develop a custom rom.
nOISEVAULT said:
As I said. I am interested in trying to work on developing roms for this device.
If you will give us a link to the SDK we can start doing that. Where is the link?
Click to expand...
Click to collapse
I have sent you a PM with the download link.
If you have high speed upload, feel free to upload it to github or other places and share it here.
Thank you
darkwingcraft said:
There is quite some documentation available (with no conditions from renesas), this might be lower level than the required level to dev a rom, but probably, scratching a bit more, there is a chance to find more, as for specific components (such as wifi, 3g modules, gps modules etc...) they have to compile with the suported devices by this SoC i can't post the link cuz this will be my 4th post, but i can tell you that what i found is this:
EMMA Mobile EV Series Pamphlet (probably worthless)
EMMA Mobile EV2 Datasheet
EMMA Mobile EV/EM User's Manual (this might be the most usefull)
On the renesas webpage is also the block diagram for the SoC, still have to do a crapload of reading b4 i can even pretend to know what needs to be done to develop a custom rom.
Click to expand...
Click to collapse
I will put the link in my earlier post then
I know what link you mean....
Regardless of what documentation you find, without the kernel source, you are not likely to be able to do anything significant or porting Cyanogen Mod over. The source is only the starting point, I believe there are a lot more work involved which may not be documentated by NEC on how to make it work.
Please see my PM and let us know here what you can manage to do out of the code.
At a glance everything in this package is published under GPL 2.0 So there's no harm in working on it.
I am working on a github repository of the source code.
OK. You can look here for the code.
I organized it in three repositories based around the tar.gz files in the SDK.
If someone wants to reorganize that's fine by me.
look here:
https : / / github.com / cAPSLOCK7
I had to write the link that way since this forum doesn't trust me enough to post links yet.
nOISEVAULT said:
At a glance everything in this package is published under GPL 2.0 So there's no harm in working on it.
Click to expand...
Click to collapse
Sounds good but even though it maybe published under GPL 2.0, I don't think anyone manage to get the code from NEC or elsewhere....
Hi Guys I just saw couple of android 8.1 test builds or alpha builds for our P2 in Android File Host website. In which the few Rom available in AFH are not mentioned or thread is not created in XDA] so that I'm just sharing it with you!
Checkout the source below to stay updated.
Source
mod edit - link removed
Edit - Few download links removed cuz they are not my work & I'm not interested in sharing it anymore.
Disclaimer:
# If you don't want to share your work, then don't share it in public.
# I'm not responsible for any Damage, Proceed at your own risk.
Is volte enabled in any of them?
I'll give a shot at the Pixel Experience ROM...Its 757mb!!
Let's see what features it holds..
I'll report back after using it
rohit1512 said:
Is volte enabled in any of them?
Click to expand...
Click to collapse
I can't tell cuz I'm not using such a carrier.
ASP02 said:
I'll give a shot at the Pixel Experience ROM...Its 757mb!!
Let's see what features it holds..
I'll report back after using it
Click to expand...
Click to collapse
Haha, have fun
Forum Rules
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!
Click to expand...
Click to collapse
thread closed and ... cleaned
#PE #ROM #OFFICIAL #10
Pixel Experience - OFFICIAL | Android 10
Updated: 24/11/2019
Mod Edit : Links removed.
Device Changes: -
- Enabled volte for Airtel/Vodafone ( Might need a wipe still not 100% if works )
- Nuked custom sf offsets
- Imported some missing radio blobs
- Enabled use_data_netmgrd
Rom changes:
- IMS Changes ( viLTE shoud work fine now )
Isn't this the same build as the other official PE ?
Well, you aren't the official maintainer. Why are you reposting builds of Dyneteve?
Thug dev
Mod Edit
2 Threads on same topic is not allowed and there is already an Official PE is released by maintainer here
May I remind you XDA Forum Rules #12
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
Thread Closed.
jackeagle
Forum Moderator