User-agent: Mediapartners-Google Disallow: User-agent: * Disallow: /search Allow: / Sitemap: http://nano7mobile.blogspot.com/sitemap.xml Nano Mobile: Source
Affichage des articles dont le libellé est Source. Afficher tous les articles
Affichage des articles dont le libellé est Source. Afficher tous les articles

Official Kernal Source by Xiaomi!! topic






Hey guys, here is the kernal source for Redmi 1s released by Xiaomi.. :D:D
It is a full source on github. :good:

Here is the link.... https://github.com/MiCode/H1S_kernel

:good:Copy and Paste URL because as I am a new user I can't post URLs:fingers-crossed:






Samsung Open Source topic






I have the N910A and live in the UK.

As i'm not on the AT&T network, i can't update OTA. I've spoken to AT$T and they said i should speak to my current network (3). I told them i cant update via them as the bootloader is locked and got pretty much a "meh" answer.

So after looking, i found Samsung's Open Source.

It seems to house the updated files - for a start, the new NK3 (im currently stuck on NIE). Im not that worried now updating, but when lollipop comes out, i'll be up poo creek.

So is it possible to flash these files from Samsung?






new open source library ogles_gpgpu: GPGPU for Android and iOS using OpenGL ES 2.0 topic






(please note: I would like to post this to the developer forum, but since I just registered, I'm not allowed to do so. furthermore, I'm not allowed to post direct links (see below))

I would like to announce a new library for GPU-based processing on mobile systems – ogles_gpgpu.

As many of you know, it is often beneficial in terms of performance and energy efficiency to execute certain processing tasks on the GPU instead of the CPU. This is especially the case for image processing tasks. ogles_gpgpu enables fast and portable, GPU-powered processing by using OpenGL ES 2.0 shaders.

Since transferring data to and from the GPU is often a bottleneck for GPU processing, platform-specific fast texture access is also implemented. The library is written in well documented, clear C++ code. An interface for Android systems via JNI is provided. Example applications show how to use this library. All code is LGPL licensed.

There are several scenarios on how to use this library: You can for example pass image data (or arbitrary byte data) to ogles_gpgpu, which creates an OpenGL texture from it. You can then process it on the GPU by applying a series of filters (OpenGL shaders) on it. This kind of rendering happens off-screen. Afterwards, you can lock the result data and obtain a pointer to it. You can then copy this data for future processing or directly analyze or modify it. Another possible scenario is to directly pass an OpenGL texture ID as input for ogles_gpgpu. This is for example beneficial if you can obtain camera frames as OpenGL texture from the camera API of your target platform (both Android and iOS allow this and example projects or provided for this). Now ogles_gpgpu can directly run the filters on this camera frame texture. This can happen off-screen or optionally on-screen, which means that the result image is also displayed to a render surface. After processing on the GPU side, you can access the result data again as described in the first scenario. By this, you can do further CPU-based processing of the result data. This is for example necessary, if certain algorithms can not (efficiently) be implemented as OpenGL shaders.

At current development stage, there are not so many image processing filters implemented, yet, but this is about to change in the future. The most important thing is that a portable architecture for GPU-based processing is available, which allows fast texture access by using platform-specific optimizations.

You can check out the project on github: github.com/internaut/ogles_gpgpu
More information can be found on my personal website: mkonrad.net/projects/ogles_gpgpu.html

Thank you.






[Q&A] [ROM] CyanogenMod 10.1.3 KANGed for bravo | Jellybean 4.2.2 | Open Source | 20 topic






Q&A for [ROM] CyanogenMod 10.1.3 KANGed for bravo | Jellybean 4.2.2 | Open Source | 20130930

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] CyanogenMod 10.1.3 KANGed for bravo | Jellybean 4.2.2 | Open Source | 20130930. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)






[Q] Do Rom makers fix bugs in Android source code? topic






Hello,

Does someone know if rom makers actually fix bugs in the Android source code? for example, can the bugs presented in android 5.0 be fixed by Cyanogen or do they have to wait for Google to release a new version?

I recently read about a memory leak in Android 5.0, and I'm running CM12 nightly and i haven't experienced any memory leak, did CM fix that?






[Q] Android source code files' location topic






I'm working on a project which main goal is to log when different features of android are being accessed.
For this I need to find the main source files of the different features.
I found the network file that I find helpful: /Android_Working_Directory/system/netd/client/NetdClient.cpp
I want to find something like that but for the gps.
Any thoughts?






Aquos crystall open source topic






i dont know this is open source for 305sh or 306sh but i hope it will be use for 2 device
https://sh-dev.sharp.co.jp/android/m...x.php?/crystal






How to send changes to cyanogenmod source? topic






Hello everybody!
Please, I need help:
I've made a complete translation of the "settings.apk" of cyanogenmod 12, but I didn't understand so much, between gerrit, github...
Can someone explain me how to make see my changes to cyanogenmod stuff, so they can merge it with the new build?

Thank you in advance






[Q] Omitting apps from CM Source Build, question.. topic






A few months back i built CM 10 (4.1.2) Wingray from source.
What id like to do now is omit/remove a couple of the apps from the build, like..

Apollo
CM File Manager
CM Wallpapers
Video Editor

I know i can just remove the apps from the ZIP after the build completes, but would to compile and build without the apps.

My question is this..

What files (and where are they) do i need to edit to remove the above mentioned apps from the build process?

any help, would be greatly appreciated.
Thanks






CM11 WITH NEW KERNEL SOURCE (CM11 2015-01-05) topic






WORKING:
ALL WORKING
NOT WORKING:
NOTHING
DOWNLOADS
http://222.73.28.48/file.data.weipan....170.99&corp=1

INSTALL:-
JUST FLASH ROM AND GAPSS BY TWRP








XDA:DevDB Information
CM11 FULLY STABLE, ROM for the Xiaomi Redmi 1S

Contributors
vishalraj08, VISHALRAJ08, VISHALRAJ08, VISHALRAJ08
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP

Version Information
Status: Stable

Created 2015-01-05
Last Updated 2015-01-04






Has anybody yet attempted to compile the 4.3 Kernel from Source yet? w/ Rant inside topic






Has anybody yet attempted to compile the 4.3 Kernel from Source Provided yet (device probably use some slight overclocking and light undervolting)? This device has amazing battery life and runs great. This is coming from somebody who has had 5 qualcomm 800 processor phones and no less than 400 phones (yes Really). Most people that i see with higher end phones use facebook and some other social apps, most of the processors are sitting idle for most people. I guess marketing is good now a days. Millions of people with 600-700 dollar phones with most processor cores times at idle and have no clue.

My wife got a Note 4 and I told her not to since most people have no clue of power/price to actual use/needs on a phone. Well yesterday, we kept running into each other in the house and I kept asking her about her battery percentage until at 3pm she started charging her phone and I told her Im at 70% (while laughing). Well she just ordered a HAM2 today. Yes I know you can get a 10,000Mah brick extension for the "high" end phones but damn. I guess I am getting older and seeing behind the hoopla.

Anyways rant off, but seriously any one look at the code yet. Im downloading it now.






[Guide] How to build from Android Source Code topic








Bare Minimum PC System Requirements:
CPU: Dual Core Intel® Pentium® Processor T4000
RAM: 4GB RAM
Storage: 70GB HDD
OS: Ubuntu 12.02 (Or any variant)
Network Speed: 2MBps

Recommended PC System Requirements:
CPU: Quad Core Intel® I5-3570 Processor
RAM: 8GB RAM
Storage: 200GB SSD
OS: Lubuntu 14.04 LTS (Or any variant)
Network Speed: 15MBps

Why do you need to be in the system requirements range?

Quote:









> The system requirements are the bare minimum you need to have to build efficiently. Anything lower than the bare minimum will take the build more than 1 Day.
> We recommend utilizing SSDs as they are the most efficient at building due to its digital format rather than the traditional HDDs where it utilizes a spinning data disc.
> We recommend a network speed of 2MBps or more due to the size of android source code being more than 10GB of data. Anything lower will take you forever to download and may put you in a risk of data corruption.
> We recommend utilizing Higher Capacity SSDs as building android uses a lot of RAM and having more of this is handy when building.
We recommend utilizing CPUs with more cores as it helps the build process to be faster.
> We recommend using Ubuntu as it is the base standard for building Android ROMs. Any other ubuntu based distros should work with building Android.




Understanding different terms

Quote:









> GIT
Git can be considered as a project planner for code. It is a requirement to learn Git. To learn git, follow this guide.
> REPO
REPO is a tool built by Google to work with GIT to download multiple repositories to your PC.
> Repositories
A repository can be considered as a container for a set of related code.
> Source Code
Source Code is made up of files that instructs different scripts to run to build a certain product specified. The rest of the source code is the resources needed to achieve this.
> CCache
CCache is a method of utilizing a specified storage space to speed up building. It can be considered to be similar as the .odex files you find in Android.
> Terminal
Terminal is a requirement as it will be the 'nerve center' of your Android Building process
> Nano
Nano is the Text Editor for Ubuntu.
> $
The "$" sign in Linux/Ubuntu represents the start of a new line of code. Picture it as a full-stop in a sentence.
> sudo
The term sudo is the way for defining root access in the terminal.




Preparing Ubuntu

Quote:









To build Android, we must install the proper drivers and software. Lets go through this step by step. From now on, anything that is highlighted ORANGE and is not a link will need you to modify it if required.

Installing Git:

Code:


$ sudo apt-get update
$ sudo apt-get install git
$ git config --global user.name Your Name
$ git config --global user.email youremail@googlotmail.com


Installing ADB and Fastboot:

Code:


$ sudo add-apt-repository ppa:phablet-team/tools
$ sudo apt-get update
$ sudo apt-get install android-tools-adb android-tools-fastboot


Installing Building Software:

Code:


$ sudo apt-get install bison g++-multilib git gperf libxml2-utils

Installing Repo:

Code:


$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo







Choosing your Source Code

Quote:









To build Android, we must choose the Source Code provider. I'll list the one's I can find below:




Syncing Source Code

Quote:









Now after choosing the Source Code you want, let's head over and prepare the repo to download their source code to your PC. Remember, URL for initializing the repo is always different so you'll need to refer and read the guide shown in their individual mini guides in the links shown above. For this moment, I'll be utilizing the source code found from Resurrection Remix.

Preparing REPO and initialize file directories

Code:


$ mkdir ~/android
$ cd ~/android
$ $  repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b lollipop


Modifying repo to download source for our device
If you're reading this but don't want to build for Huashan, consult your respective developers at your device's xda forum

Code:


$ cd ~/android/.repo
$ git clone https://github.com/Ultrax5/local_manifests.git
$ cd ~/android


Downloading Source Code
This will take a VERY long time and I probably recommend you go and do other entertaining things while this goes on.

Code:


$ cd ~/android
$ repo sync -j8







Applying the necessary patches

Quote:









For other devices, this will not be needed unless the developer states that a patch is required.

Code:


$ cd ~/android/device/sony/huashan/patches
$ chmod 755 apply.sh
$ ./apply.sh







Building Android

Quote:









Now to the most important part of the guide, BUILDING! If your PC hits the minimum requirements then it will build for about 4-6Hours while if your PC hits the Optimal Recommended Requirements, the build will take about 1Hour.

Obtaining Pre-Builts from CyanogenMod
Only use this if you choose a source that was based off CyanogenMod

Code:


$ cd ~/android/vendor/cm
$ ./get-prebuilts


Building Android
Change Huashan to your device code-name if you're building for other devices. It is recommended to take a look at the output as it may pin-point errors as they pop up.

Code:


$ cd ~/android
$ . build/envsetup.sh
$ brunch huashan







Obtaining the Final Product

Quote:









Congratulations on making it this far! Once the build process is completed with no errors do the following;

> Open up the file manager app of your choice
> Navigate to this directory; ~/android/out/product/huashan/theromzipwilllooklikethis_1242142132.zip

Once you've located the zip file, rejoice! You've successfully built a ROM direct from source! Now, you can flash the zip using your recovery and maybe even post it on XDA!




Epilogue

Quote:









Thank you for following and reading the guide! If you post a ROM by using this guide, please do leave a credit for me and for those who didn't, leave a Thanks! :D

If you're ever wondering what my Build Environment is like, here's a look at my specs.




PC TYPE: Custom Desktop
CPU: Intel I5 4670k
RAM: CORSAIR Vengeance 8GB
Storage: WD Black² Dual Drive
GPU: Asus GForce GTX 780 [Unimportant in Building]
Motherboard: ASRock 990FX Extreme9
PSU: RM Series™ RM1000
Casing: Cooler Master Cosmos II

[Yes I know, this build might be overkill but who cares :P]






Credits
  1. NexusPrime

  2. MrSteve555

  3. Pec0ra

  4. Other XSP Developers

  5. XDA Developers

  6. Cyanogenmod Build Guides

  7. Resurrection Remix Team