Database Info

MTK 6589 and MTK 6589T (overclocking possibilities)

I was looking at the mt_cpufreq.c file in the leaked kernel source for the MTK 6589 SoC (the one running at 1.2 GHz), at https://github.com/varunchitre15/MT...atek/platform/mt6589/kernel/core/mt_cpufreq.c
I noticed there were frequency settings above 1209 MHz defined there. The highest one, DVFS_F0_0 goes above 1.7 GHz.
The code that seems to define the maximum frequency starts on line 1573 of that file. It relies on the returned value of PTP_get_ptp_level to define it. Since PTP_get_ptp_level is just a external header on that file, I needed to search the git repo to find its definition. Turns out it is in this file mt_ptp.c. Pay special attention to line 1018 and below: https://github.com/varunchitre15/MT...ek/platform/mt6589/kernel/core/mt_ptp.c#L1018
There's this interesting bit:
Code:
#if defined(MTK_FORCE_CPU_89T)
return 3; // 1.5GHz
#else
By returning 3, this function tells the frequency scaling driver that the CPU can go up to a 1.5 GHz clock.
I think I read the 6589T also has a higher GPU clock, and it can handle 2 GB of RAM with no problems. I'm not saying that the difference between the 6589 and the 6589T is just a kernel config, in fact, the chip most likely got a new revision. This source code leaked before there was any talk of a turbo revision of the 6589, so I think it's safe to assume that on newer code trees there may be fixes for the 2 GB of RAM and a higher GPU clock.
But I wonder, if the 6589 (not T) is able to go up to 1.5 GHz or even 1.7 GHz. It would be good if someone could compile that kernel with some modifications to make it think it will be running on a 6589T (adding a #define MTK_FORCE_CPU_89T should be enough) and see if it works fine. Since that source code came from a Acer model, maybe it would be easier to start tests on that device (because we can be sure the source is 100% compatible). I think it may run, but it may heat a lot or it may drive the voltage of the CPU up to a point where the phone's PCB is not prepared to deliver, causing damage (maybe the T revision chip fixes this).

have you done any more digging or testing on this?
Just noticed that Jiayu have released a MTK6589T version of the G3S for only $5 extra - could it be just a simple software unlock?
thanks

My guess is that it really is only a kernel setting considering that the Jiayu G3S comes with both chips within 2 weeks. Besides this is a really easy way for mediatek to sell a wide range of SoC's (just varying the voltages/clockspeeds). The main thing I wonder if this also controls the clockspeed of the GPU, since that clock is different as well, considering the MKT6589 and MKT6589T.

http://www.ini3e.com/thread-2610-1-1.html
This chinese article confirms that the only difference is clock speed.

It would be really good if someone who can already compile custom kernels for any MT6589 phone, could make that little modification and check the results - worst case scenario, the chip would get too hot and break forever... but since it seems to have a lot of temperature monitoring in place, I don't think that would happen.
I could do it myself, but I'm not going to download 8 GB of Android source, on my limited home connection, just to apply the MT6589 patches available on GitHub, which probably wouldn't work out-of-the-box since they are for a Acer phone and mine's a Zopo 910.
Bothering people at Zopo to do it is out of question, since they are interested in selling the Zopo C2 which comes with this "turbo" kernel config.
As for the GPU clock, on this kernel source there doesn't seem to be anything controlling that based on the MTK_FORCE_CPU_89T define. But this may be just because this is an old source tree - the one they have been distributing for their clients more recently, for the 6589T, may already have the changes for the GPU clock.
The ideal situation would be to have a kernel which can allow all the possible CPU and GPU frequencies, and these would be controlled and limited on the userspace.

It would be awesome ! Please devs, do something for us

is there anyone working on this

kartikoli said:
is there anyone working on this
Click to expand...
Click to collapse
I looked at it shortly, and noticed a lot of stuff is missing to compile it.
But why not look at it yourself?
Start by git cloning the cm10.1 tree and compile for a device that is supported, to get an idea of how it works.
People who manage to compile the source, please post, because from there we can come close to building CM10.1.

The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10

gbl08ma said:
The sources on that Github are meant to be merged with the JB source tree, you're aware of that when you say it's missing things, right?
Here are sources for another MTK 6589 device:
http://forum.xda-developers.com/showpost.php?p=43650399&postcount=10
Click to expand...
Click to collapse
this group is working on a Cyanogenmod for mtk6589 devices...http://forum.xda-developers.com/showthread.php?p=41345830

http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.

gowtham121 said:
http://wikogeek.com/ (Select CINK 5) complete kernel source (800 Mb compressed) with build scripts.
Click to expand...
Click to collapse
The Cink Five is a French MTK 6589 (not T) phone. Specs identical to my ZP910 except for the screen (higher resolution). Also, on Wiko Mobile's website they claim it supports USB OTG, which would be interesting to implement on other MTK phones.
Now downloading the sources (let's hope the connection doesn't fail, and that I don't spend all of the quota for this month... sigh).
EDIT:
I am now compiling this kernel tree, which is the most complete I've ever seen. Funny thing, this one doesn't have the 89T part I mentioned on the OP.
Ideas from http://forum.xda-developers.com/showpost.php?p=43861751&postcount=64 are proving to be useful when compiling this 6589 kernel (mainly the kalOidComplete errors thing).
Of course I'll never be able to get this kernel to boot on my Zopo, as I'd have to guess all of the kernel config including things like GPIOs... but getting a binary will at least be fun.
And in case you never looked into a Mediatek code tree, this thing is a horrible mess (something common to most OEMs and SoC manufacturers, anyway). And this is just the kernel... I don't even imagine how it would be if it also had the preloader, lk, etc. sources...
BTW, I just got a "**** Successfully built kernel ****" message, but then it says "Cannot open file /arch/arm/boot/zImage". Will have to investigate.
EDIT2: I managed to compile a kernel from the Cink Five source tree.
Interesting aspects:
This kernel source is more incomplete when it comes to CPU freq scaling than the one from the Acer Liquid E2 available on Github (and which is missing many of the scripts needed for compilation). For example, it doesn't know of any speeds above 1209 MHz. The source tree on GitHub is effectively more recent.
This kind of saddens me. It means that at some point, Mediatek wrote the code thinking the CPU wouldn't go over 1.2 GHz. Then they may have added the 89T-specific code later, only when they developed a physically different die that effectively allows for higher clocks. And so 6589 and 6589T may have more differences than just a kernel config.
You can see that new DVFS configurations were added to the source code at some point.
From mt_cpufreq.c @ Cink Five source tree (presumably before):
Code:
#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV
From mt_cpufreq.c @ Acer Liquid E2 source tree (presumably after):
Code:
#define DVFS_F0_0 (1703000) // KHz
#define DVFS_F0_1 (1599000) // KHz
#define DVFS_F0_2 (1508000) // KHz
#define DVFS_F0_3 (1404000) // KHz
#define DVFS_F0_4 (1300000) // KHz
#define DVFS_F1 (1209000) // KHz
#define DVFS_F2 ( 988000) // KHz
#define DVFS_F3 ( 754000) // KHz
#define DVFS_F4 ( 497250) // KHz
#define DVFS_V0 (1250) // mV
#define DVFS_V1 (1200) // mV
#define DVFS_V2 (1150) // mV
#define DVFS_V3 (1050) // mV
#define DVFS_V4 ( 950) // mV
This is just a very small part of the differences between the two code trees.
But even if the 6589 can't overclock, the 6589T apparently support a speed of 1.7 GHz (DVFS_F0_0)... unless they added that just for testing purposes.

All we now need is someone with a Cink Five to join this forum...Hopefully someone will be willing to test your kernel..
Anyone out there with a Cink Five???

Apparently the Cink Five is targeted at the French market, so probably one will have better luck asking in a French Android forum.
Any French speakers here?

Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !

frans0023 said:
Hi I'm a Wiko cink five user from France. I can give a try but I need stability. If you think it's stable enough, no problem, I can test it.
Thank you for your work !
Click to expand...
Click to collapse
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.

gbl08ma said:
To be honest, I think it wouldn't even boot, let alone be stable...
But if you can make a backup of the existing boot.img, then flash my one, and don't mind spending a hour or so without the phone, you could revert to the original boot.img if mine didn't work.
I don't know if Wiko released any updates for the Cink Five or if you have one installed, but that would make it easier to get the current boot.img for backup.
Click to expand...
Click to collapse
No problem for me, send me the file and I will give a try. Just tell me what I have to check, maybe you want the logcat ?
Only boot.img is written when you flash a kernel ?
If it's only that, I could boot on recovery (twrp) and backup the file with "adb pull", then push yours ?
I have to sleep, good night
Envoyé depuis mon CINK FIVE avec Tapatalk

Actually, boot.img is the name of the file on the computer, to be updated with SP Flash tools. I don't know if Wink ever released an update to be flashed this way (but since you have TWRP, probably you have used it).
On the phone (or with recovery), I know a kernel can be flashed with a update.zip.
Right now I don't even know how to create a boot.img file, I only have the zImage. I'm trying to get a way to repack my boot.img so that I can try it on my Zopo...
And then I'll have to solve the problem of the kernel modules (these may be harder to restore since they are in the system partition I think)...
Also:
Is it just me, or the Cink Five is the same as the Fly IQ451? Turns out the zImage I compiled was with the config for the s9201b board, which is the IQ451.
From the pictures of the case, it seems to be the same... but, with Chinese phones, the case means little.
The source tree came configured to use the tinno89_jb config but I changed it because I couldn't compile with it.

Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)

gowtham121 said:
Aw yeah, you atleast tried to compile the kernel Let's hope the CINK Five guy can test your kernel (P.S: A engineering build please, so that I can access Thermal settings in MTK Tools)
Click to expand...
Click to collapse
I think you guys still haven't understood very well that my kernel most likely won't even get to the Android boot logo (I bet it will stop in the early kernel boot stages with some kernel panic).
Furthermore I need a boot.img for the Cink Five so I can put my zImage in there. Otherwise it will never be compatible.
Also, I think the build type is set on the Android building process. I can only build a kernel. I don't have a good enough internet connection to download the Android source, and my computer with 8 GB of RAM lacks the necessary 16 GB (!!!) for compiling.

[Completed] help adding driver to kernal

Hi guys
I am new to android and i need some help. Apologies if i have posted this in the wrong place.
I manufacture and supply large touch screens to special needs schools and in the past i have used multitouch overlays that came with a mini pc android called istick by PQ Labs that were coded to work as multi touch. now i have changed touch panel product i need an android pc to work with it.
I am thinking of using a MK809iv and the company that supplies the overlay has sent me the mods that need to be made to the kernel but i have no idea how to do this.
Here is what they sent me.
Transplanting under Android4.0 For IRMT Multi Touch Frame Driver V1.1
The following method is suitable for the kernel which above Linux 3.0, we take an example of Kernel 3.08.
1. Add manufacturer ID and Device ID in the 352st line of “drivers/hid/hid-ids.h”
#define USB_VENDOR_ID_IRMTOUCH 0x23c9
#define USB_DEVICE_ID_IRMTOUCH_SSERIAL 0x5666
2. Add device according to put the following program in the 669st line of “/drivers/hid/hid-multitouch.c”
/* IRM Multi-touch panel */
{ .driver_data = MT_CLS_CONFIDENCE,
HID_USB_DEVICE(USB_VENDOR_ID_IRMTOUCH,
USB_DEVICE_ID_ IRMTOUCH_SSERIAL) },
3. Add special protocol support in the 1392st line of “drivers/hid/hid-core.c”
{HID_USB_DEVICE(USB_VENDOR_ID_IRMTOUCH, USB_DEVICE_ID_IRMTOUCH_SSERIAL) },
4. Configuring the kernel. (menuconfig)
Firstly enter Device Drivers, then enter HID Devices ,then select Special HID drivers. Build-in HID Multitouch panels . ( select “*” )
Save and exit.
5. Compile the kernel and update the mirror of android 4.0
Shanghai IRMTouch Technology Co.,Ltd
2012.8.31
Any help would be greatly appreciated
Thanks
Ty

Hi there,
I see you already founded the right place to ask, so keep wait an answer there:
[Q] Help with kernel adding driver
Good luck
Thread closed, thank you

Lollipop Source - Official Nvidia Repository

The developer site is still listing KitKat as the newest build, so here are the links to the instructions to build Lollipop using the official source:
Lollipop 5.0: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r1-partner
Lollipop 5.0.1: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r2-partner

Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.

berryman13 said:
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
Click to expand...
Click to collapse
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.

twistedumbrella said:
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
Click to expand...
Click to collapse
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!

berryman13 said:
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
Click to expand...
Click to collapse
Even without already having the branch name, it's just a matter of going to http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=summary to find it

Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool

diigibio said:
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
Click to expand...
Click to collapse
I'm trying to figure out what's up with it now. I know when I synced it was r1, and tlk/shieldtablet.xml was valid.
Hopefully I can track down why it is coming back invalid in r2.

Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!

diigibio said:
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
Click to expand...
Click to collapse
Same to you. It updated ok but now I have to see if it'll re-init. It may be a delay on their end. The readme for the portable was up a week before the source.

Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks

diigibio said:
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
Click to expand...
Click to collapse
Best bet is to either find something you like and merge it or try to find something similar and recreate it to start. Once you get comfortable, then start coming up with your own.
Building from source is mostly Java for modifying with some C for drivers and such. Usually when you have a device configuration already set up, though, the C part is already done.

Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.

diigibio said:
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
Click to expand...
Click to collapse
Glad to hear it's all up and running. Best of luck!

twistedumbrella said:
Glad to hear it's all up and running. Best of luck!
Click to expand...
Click to collapse
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.

entelekia said:
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
Click to expand...
Click to collapse
It looks like they are still working out a few issues with new updates. I don't maintain the source, so the only advice I can provide is to keep on eye on nvidia's gitweb for when they publish a solution (or occasionally sync and try over), or attempt to fix it yourself (which usually only works if there is an issue with the code, not code missing altogether).

Compiled! I have resynchronized all the project from scratch from git repository.
I'm going to test the compiled ROM in my tablet, but I suppose, I have to provide almost the essential pack of Google apps (basic providers and play services).
I think to flash *.img files, except recovery.img (I'm on TWRP), and then install from TWRP PA Gapps. Is this approach correct?
Thnx in advance and regards.
EDIT: No luck booting custom rom (TWRP nor stock recovery...)

Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml

GethPrime said:
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
Click to expand...
Click to collapse
Anyone managed to build this one yet? Its not working for me..

[Completed] AT&T Galaxy Alpha g850A US Variant Possible Root Exploit Found

Hi Mods,
I do not have permissions to post in the development forum so I ask that you move this thread accordingly.
I have been researching the AT&T Galaxy Alpha sm-g850a variant in order to gain root access and, as you might know, have found absolutely nothing out there. All other international variants have been rooted Except the A model...which is what I am stuck with. I found a recently released CVE that states it is not patched until Lollipop 5.0 and allows a malicious intent request to take over SYSTEM permissions. I have been able to get the intent code into an app without bricking the phone and am having some NOOB java issues as I'm not a professional programmer. Any interest in helping finish this exploit would be greatly appreciated. A few code snippets below:
import android.accounts.NetworkErrorException;
import android.app.PendingIntent;
import android.accounts.AbstractAccountAuthenticator;
import android.accounts.Account;
import android.accounts.AccountAuthenticatorResponse;
import android.accounts.AccountManager;
<intent-filter>
<action android:name="android.accounts.AccountAuthenticator" />
android.content.Intent intent = new Intent();
intent.setComponent(new ComponentName("com.android.settings","com.android.settings.accounts.AddAccountSettings"));
AccountManager.get(this).addAccount(
accountType,
null, /* authTokenType */
null, /* requiredFeatures */
addAccountOptions,
null,
mCallback,
null /* handler */);
mAddAccountCalled = true;
PendingIntent test = (PendingIntent) options.getParcelable("pendingIntent");
Intent newIntent2 = new Intent("android.intent.action.REBOOT"); <---testing---> somewhere in here I need to drop the SU binary and all of that good stuff.
try {
test.send(mContext, 0, newIntent2, null, null);
} catch (PendingIntent.CanceledException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
There is more code obviously. Posting some main parts to see if anyone is interested in helping.
w/respect-PitPin

Can't forget the credit for discovering this vulnerability:
Credits: Wang,Tao(Scloud) - seclist.org

Here is my NOOB showing. Wouldn't this mean I am on the right track and my app took "system root" privileges?
7386-7386/com.pitpindesigns.modpit.pitpin E/dalvikvm﹕ >>>>> com.pitpindesigns.modpit.pitpin [ userId:0 | appId:10248 ]
Nope...1000 would be root.

Sir,
Here isn't the right place for this type of threads so please open a new one here:
xda-developers -> Android Development and Hacking -> Android General
Good luck

[rom][aospa][unofficial][7.2.2][bacon]

I have almost finished compiling the ROM but need some help with an error then it'll be ready.
Here's what's happening when I build it:
[ 0% 90/18970] Docs droiddoc: out/target/common/docs/api-stubs
DroidDoc took 16 sec. to write docs to out/target/common/docs/api-stubs
[ 0% 91/18970] Compiling SDK Stubs: out/target/common/o...IBRARIES/android_stubs_current_intermediates/classes.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[ 0% 93/18970] Building with Jack: out/target/common/ob...LIBRARIES/framework_intermediates/with-local/classes.dex
FAILED: /bin/bash out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex.rsp
Out of memory error (version 1.2-rc4 'Carnac' (298900 f95d7bdecfceb327f9d201a1348397ed8a843843 by [email protected])).
GC overhead limit exceeded.
Try increasing heap size with java option '-Xmx<size>'.
Warning: This may have produced partial or corrupted output.
[ 0% 93/18970] Compiling SDK Stubs with Jack: out/targe...BRARIES/android_stubs_current_intermediates/classes.jack
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Build failed!
Total time elapsed: 10 minutes (652.687489167 seconds)
I cannot seem to locate the java heap size parameter file to modify it. A little info will help out. If not I'll figure it out on my own soon and have the latest build ready for flashing. Thanks.

Official? Oh please...

SirSoviet said:
Official? Oh please...
Click to expand...
Click to collapse
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?

Techie Android said:
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?
Click to expand...
Click to collapse
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.

SirSoviet said:
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.
Click to expand...
Click to collapse
Okay I was not aware of that being the case. I understood official to mean it was unmodified and built from the source. I'll change it to unofficial since I'm not connected to AOSPA. Thank you for pointing that out.

placeholder threads are not allowed on xda where are the moderators when we need them?
Read the RULES NEXT TIME!!!!

Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?

Techie Android said:
Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?
Click to expand...
Click to collapse
Rules are rules.. There was no trash talk, the only poor attitude is yours. I hope you'll resolve this here as well as with any future posts you make..
I've already reported this thread, lets keep this respectful until everything gets fixed..
Thanks

Thread moved to Q&A section at this moment, if later the ROM is released, please report it to Mod Team and we will move it back to develop section.
And please be reminded to keep the discussion as civil as you can.