Database Info

Renesas Emma EV2 Open Source Project

Hi,
Altough this is just the skeleton of it, let me share what I've set up until now.
I've also started a dedicated Google group here: https://groups.google.com/forum/?hl=en&fromgroups#!members/renesas-emev-osp
Anyone interested in contributing to develpment, plesae join!
1) Android
https://github.com/ffxx68/Renesas-device_emev
This is the entry-point to the GitHub repositories where I would put all the modification to the AOSP code which are specific to the Renesas EMEV for our Open Source Project.
Have a look at the README for further details and follow the progress, or open discussions, on our Google group.
2) Kernel
https://github.com/ffxx68/RenesasEV2-BSPGB-Kernel
This is the public GitHub repository for the 2.6.35.7 Kernel source code. It is customized to emxx code and it includes for the moment only the LCD patch that is necessary for the most common tablet (the kernel base code is aimed at the development board instead).
Same as above, anyone can contribute directly here.
3) Bootloader
https://github.com/ffxx68/RenesasEV2-bootloader
This is the public GitHub repository for the bootloader source code. It includes a patch for the 4 DDR tablet models.
I don't expect this to be changed much, but anyone can contribute directly pushing new files over here too.
4) Packaging
Some more details about how to wrap-up a fresh build and make a firmware for the tablet are found in the README mentieod above.
I've managed to boot Android from an SD card (see here: https://github.com/ffxx68/Renesas-BootSD) and I think a similar approach should be followed, at least for initial testing.

Kind of late to the party, but I'm really interested in this project... I applied to the Google Group, but I notice that the EV2 AOSP page you listed is gone... is there a specific reason for this? I would really love to contribute to this.

Hi, and welcome aboard!
I have edited a couple links above, which have changed a bit since then.
Thanks

I'm facing a problem with the touchscreen driver, which I have filed in the group list as well:
https://groups.google.com/forum/#!topic/renesas-emev-osp/smcwddwvNDo
(answer over there, if possible).
I can't understand why the driver for the touchscreen (found in drivers/input/touchscreen/pixcir_i2c_ts.c) is not loaded during the kernel init stages.
The touchkeys driver (ekt2201) is very similar in code structure and it's loaded as expected, while the _probe function of the PixCir is never called. This is the fragment from the dmesg kernel log:
...
<4>ekt2201_init
<4>ekt2201_i2c_ts_probe
<6>input: ekt2201 as /devices/i2c-0/0-0010/input/input0
<4>ekt2201:i2c_add_driver 0
<4>emxx_tsixcir_i2c_init
<4>emxx_tsixcir:i2c_add_driver 0
...
Note as the input device is created for the ekt2201 as the _probe is called, while the same doesn't happen for the pixcir.
Anyone with a clue?
thanks

Hi,
if anyone's interested in testing an experimental, pre-alpha version of the Open Source GB and Kernel build, leave a message here:
https://groups.google.com/forum/?hl=en&fromgroups#!topic/renesas-emev-osp/Mmd8r-YMaNo

Porting to JB has started: https://groups.google.com/forum/?fromgroups=#!topic/renesas-emev-osp/XSdLmPgD9Og

Floss Development [x86 OS DEV AHEAD]

Hey Just wanted to announce a new OS dev, all code will be pushed to Github as free and opensource code (yet to choose a license).
To get off the ground I will be using this: jamesmolloy. co .uk/tutorial_html/1.-Environment%20setup.html It is a great starter to get int OS dev.
Don't start about the tutorial, its to get me off the ground with the development, from there the rest of the information will be derived from osdev.org.

Essential prerequisites for X2 Android development [Crowdsourcing]

There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too. Aka device
Kernel sources for the device. Aka kernel
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device. Aka vendor
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
Thanks to T4ufik_Hidayat, Here is vendor packages: https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
DONE! :good:

Nice effort

You are our only hope
As we have no real devs for this device and the device wasn't released globally, u r our only hope. I request u to build the kernel with device tree that we need so much to port any real android rom like AOSP , please. Frozentears was working on that, You can contact him as well.
Again, I request you, please make us a custom kernel so that we noobs can start porting KitKat/Lollipop for our beloved X2DS, u r our only hope because we see no other developer here for this device.

danialbehzadi said:
There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too
Kernel sources for the device
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device.
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
No known instant or effort.
Does anyone know how to extract it? Can anyone contact to Microsoft mobile and get them and upload it to Github?
Click to expand...
Click to collapse
Here is for proprietary https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
for Android source tree, try to use CyanogenMod.
maybe you can help people to make the complete rebuild of CyanogenMod with full fixed from bugs

danialbehzadi said:
There is 3 packages needed for any device for an original Android development:
Android source tree, preferably the original as with OEM devices but CyanogenMod or independent ports are enough too. Aka device
Kernel sources for the device. Aka kernel
Vendor proprietary drivers, which make the GPU and various sensors work. If not explicitly available for download they need to be extracted from a running device. Aka vendor
If these three packages are all available, making new roms will be easy for developers. Please co-operate to gather all of them here to be a resource for android developers.
If we could achieve this goal, I would port the Ubuntu OS for Nokia X2 and share it here with you
====
Progress:
Android source tree
No known instant or effort.
Can anyone contact to Microsoft mobile and get the Android source tree for Nokia X2 and upload it to Github?
Kernel sources
here is kernel source code for Nokia RM-1013 2.0.0.11: https://github.com/danialbehzadi/Nokia-RM-1013-2.0.0.11
Due to Microsoft mobile statement, there is no difference in kernel between 2.0.0.11 and 2.1.0.13.
DONE! :good:
Proprietary drivers
Thanks to T4ufik_Hidayat, Here is vendor packages: https://github.com/cm-nokia-x2/proprietary_vendor_nokia_ara
DONE! :good:
Click to expand...
Click to collapse
https://github.com/cm-nokia-x2/
android_kernel_nokia_msm8610-kernel source
proprietary_vendor_nokia_ara-vendor
android_device_nokia_ara- device(boardconfig.mk, other configs)
And here is the manifest
https://github.com/cm-nokia-x2/android_local_manifest

Look for devs to work with

Hello guys,
Once again I bring with me some nice tools/ideas.
I am looking for devs to work on a new version of Cloud_Commander as posted in the link title. We are to implement new features that should counter other phone flashing devices.
The tool will be free as always , and will thrive from community effort.
Currently the tool has a load of features, I intend to remove/upgrade some of it's current feautres (Re-Animation Edition).
The proposed feautres:
Implement MTK Flashing withing the core. Update F2SEARCH to use Google drive instead of rapidgator to cope with expiring files(Am almost through with this part) The new f2search will allow everyone to upload flashfiles to google drive with one click and share them to the public F2SEARCH search engine. It will enable uploaders to automatically earn via adds embed in the links.
Mtk Flash tool.
The Mtk flashtool will also have a dev console that will allow devs to add custom programming procedures to flash devices.
Like reset frp with custom format address for specific device added by a dev .
It will be almost the same as the current adb dev tools.
Fix The remote device view with some new code that I found to allow easy use of device like "Vysor".
I have some code that can communicate with modem and even dial numbers in some samsung devices. I intend to implement free samsung frp remove ability, maybe even go as far as cert writing capabilities to allow repair of broken devices.
All this features are to make the software perform competitively with existing non-free flash tools.
All this work is for the community, I could use some help especially to the mtk flashtool.
XDA:DevDB Information
[Tool] Cloud_Commander Ver 1.8 (Re-animation Edition), Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Beta
Current Stable Version: 1.7
Created 2018-01-19
Last Updated 2018-01-19

thread closed until any link will be available @kenkitt pm me if you have any links to share and to reopen it or , if not, I can move it to the Android General section in case this thread is only a discussion, thank you !

List with devices having official releases of TWRP, LineageOS and other roms

Dear community, I think this list is the first of its kind.
Purpose
The main purpose of the whole project is to help newcomers find the relevant TWRP and Roms for their devices and ultimately make the installation process as easy as possible. This list also serves the purpose of giving an overview of devices which can run custom android roms for people who do not have such a device yet and would like to buy one but don't know which ones to choose from.
Goal
Its goal is to contain as many devices (with name, model name and codename) as possible which also have official releases of TWRP, LineageOS, Resurrection Remix, Omnirom or Carbonrom. The list also contains some working TWRP builds and roms that I saved to a personal archive some time along the last years - mainly for older devices without newer roms and for good roms that just did not made it to an official release.
The Free-Droid project
The creation and continuous update of this list is tied to the Free-Droid project, mainly because it is scraped and put together by the same ruby code that is used inside the Free-Droid One-Click Rom Installation Assistant.
Why only these chosen roms? Can another rom be added?
The choice of roms showing in the list is constrained by these factors:
free and open source (no google apps included)
The website with the official releases can be scraped (programmatically read and evaluated) with ruby code down to the individual download links for the roms
(Preferred) The rom zips have signature spoofing support or are patchable with the NanoDroid patcher
A lot of roms fail at one of these constraints. I tried to add crDroid, but their website is pure javascript and can't be scraped easily. AospExtended was added by using the OTA API, but it turned out that the API server is way too unreliable. What might be possible and get added are mokee and /e/.
Updates
The list is automatically updated weekly and should always point to the latest available roms.