yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] Master Limbe:
Honestly, but if you think about it, the Xperia S was the first Sony smartphone. For them to have supported official updates up until that point was actually quite a good thing. We all know how short a phone's life span is; flagship today, archaic tomorrow. Still, we can't help but feel slighted. If anything, they should have pulled through with the ASAP project. That aside, I have Kit Kat running on my Nozomi, there are literally hundreds of ports out there of official apps, inclusive of those "exclusive" to the latest flagship. Personally, I have no reason to complain.

Indeed, it is I.
[Sony Xperia S, Acro S, Ion] steve's xperia:
No more for old Sony ( not Ericsson) product now we have to look or buy the new Z2
[Sony Xperia S, Acro S, Ion] Erix_code:
help!!

i have updated to 4.1.2 and now my sdcard is gone!! i connected to PC and it wont open either!! everything else is working fine!!

thanks for any help
[Sony Xperia S, Acro S, Ion] nageswarswain:
How do u updated?
[Sony Xperia S, Acro S, Ion] c0ntagi0:
RE. Tegra's horrible at battery life

Well, you're wrong. I have a LG Optimus G with a Snapdragon S4, and it was and still is blazing fast. The battery's probably not at it's peak, but that's because it's a 2 year old phone. Funnily enough, I bought the LG to replace the HTC One X because it couldn't keep it's charge up after a couple of hours of doing absolutely nothing. The HTC One X, which I also had, used to start up all fast, but after a few apps were open, the phone would start to warm up to toaster levels and everything, and I mean everything, would be slow to start and respond. By this time, I would be frantically looking for a charging point. My Nexus 7 is currently in the same situation, slow to respond, slow to start, slow to use and dies quickly.

You're probably attributing the Xperia T's sluggishness to the chipset, when it is probably the manufacturer (Sony) that is at fault. From a Sony Xperia S, to Sony Xperia Tablet Z to a Sony Xperia Z2, I noticed their phones start tending to lag and drop performance to snail's pace after the first major OS update. But HTC and (probably) Google are right on top when it comes extracting maximum performance from their devices, so I'd lay the blame squarely on the chipset.
[Sony Xperia S, Acro S, Ion] maddboss:
You're wrong. Why do you writing about something that you don't know?

My old Xperia s has that problems that you mentioned (battery drain very very quickly, and everything is slow) but it's 4 years old.

And now I have an Xperia Z2 for nearly 2 years. It's very fast, not slower than it was at the beginning, and battery life is nearly as good as it was. I could play about 5-6 hours and still remain some charge in the battery, and if I don't use it for playing it could last 2 or more days, depending on how much I use my phone (2 days with average using and no playing)
[Sony Xperia S, Acro S, Ion] c0ntagi0:
While you may have experienced better battery life owing to your usage, it has been different for me. I used to enable stamina mode and even after hours of reddit, navigation, calls, messaging and gaming, I could rely on the Z2 to take me through from 6am until 12am. After the update to MM, there was no stamina mode and the battery died by 4 - 5pm. That's what I meant by bad battery life.
[Fairphone 1] Unrelashade:
Even though it was said that the Fairphone will be completely open, the sourcecode of the MediaTek chip (MT6589M) is still not available (update: that was true for the time of writing. Luckily as of now, sourcecode is available and a custom ROM is in the making, see Developtment and Original Development Subforums). The link to the linux sourcecode except for the MediaTek part is here:

Great to see that. However, we need MediaTek sourcecode for custom ROMs if we don't want to reverse engineer (which is a lot of hard work and may even be considered a gray area on legality, I think)

Thanks to [MENTION=2843224]dbrgn[/MENTION] for bringing this up:

So

Petition for MediaTek to release the sourcecode

http://www.ipetitions.com/petition/aosp-support-for-mediatek-devices/

Does anyone know if it's possible to persuade MediaTek to release the code, because they use Linux (GPL)?

Why don't they release the code? Can it be exploited or do they think there is a risk this can be used against them by other companies? Or do they just not care to do a little work?

Sony has managed to release the sourcecode of the MediaTek inside the Xperia C

http://developer.sonymobile.com/dow...es/open-source-archive-for-build-16-0-a-0-36/

So we and Fairphone can do it too!

(Mistake by me, it's just the kernel. Thanks chrmhoffmann for pointing it out)
[Fairphone 1] dbrgn:
Yes, we definitely need the full sources. One of the reasons why I bought the Fairphone was its alleged openness. If we can't get the Mediatek sources, the promise of a "completely open phone" is nothing but empty words.
[Fairphone 1] chrmhoffmann:
That Sony code is just the kernel. It's clearly stated on that page you link to.

Chris
[Fairphone 1] JY-G3:
More threads about this:

Operation RMD - To Support & Reward our MTK SoC Developers: http://xdaforums.com/showthread.php?t=2164959

OmniROM For MTK Devices: http://xdaforums.com/showthread.php?t=2483238

MTK 6577 Sources [Complete]: http://xdaforums.com/showthread.php?t=2560714

MediaTek Contact URL: http://www.mediatek.com/_en/08_info/03_contactUS.php
[Fairphone 1] zelendel:
You guys have to remember any device out of China is not going to be held to the GPL.

Bat cave One
[Fairphone 1] Entropy512:
Promising openness and choosing an MTK chip are completely conflicting right now.

MTK is one of the least open source friendly chipset providers out there.

1) Their kernel is often full of binary blob modules. Sadly, in many cases, blob modules ARE legal. See the infamous Samsung FSR driver on the GalaxyS family.

2) Their kernel source code is a disorganized mess

3) If you have a friendly OEM that will leak MTK's complete Android build tree to you:

a) They will only build as-is with an oddball and VASTLY outdated Ubuntu configuration

b) They're an even more disorganized mess than the kernel sources and will cause severe brain damage if you try to read/understand them without taking breaks to work with a less screwed up source tree

c) Even their OEMs only get statically linked binaries for many components. For example their hwcomposer "source" is just a wrapper around a blob

d) They have yet to support an Android release newer than 4.2 - partly because it looks like they initially wrote stuff for Android 1.x and have never updated their sources properly to fit in with newer versions of Android. (They have been hacking Android sources to be compatible with their junk instead of the other way around). For example, they still don't use device trees.

Even with an OEM that is cooperating significantly with developers (like Oppo), working with MTK devices is slow and extremely agonizing.
[Fairphone 1] ancdix:
Kernel Source ??

Good day everyone,

I was looking around for useful information and I stumbled over this -> https://github.com/varunchitre15/MT6589_kernel_source

Maybe I'm wrong but isn't that what everyone is looking for?

If not... well I'm sorry about pointing out the wrong stuff :(

Cheers,
[Fairphone 1] Entropy512:
no

Seriously, did you even bother to read the earlier posts in this thread?
[Fairphone 1] ancdix:
And it's gone :) Nexus 5 here I come.
[Fairphone 1] FlamingoKid:
There are new sources posted on the Fairphone website. See the thread with technical details.

Hope it is complete now, as the first compilation attempt failed...
[Fairphone 1] Entropy512:
Kernel source is better than many MTK OEMs, but it'll still at best get you custom kernels. AOSP-derivative builds (CM, Omni, etc.) are right now far away.

(In case you haven't figured out - some of the Omni developers have a "complete" MT6589 source tree. I use "complete" in quotes because while it will build 4.2 on a properly configured machine, it is a mix and match of tons of blobs and all sorts of horrible hacks that result in it being a nightmare to integrate into any 4.3/4.4 AOSP-based project. Yes, even with an OEM giving us everything they have access to we're barely able to get 4.4 to boot on MT6589.)

https://gerrit.omnirom.org/#/q/status:open+branch:android-4.4+topic:mt6589,n,z for an example of the terribad hacks required to get it even to boot
[Fairphone 1] FlamingoKid:
Ah, so this is more a Mediatek issue (provided with full 'sources' it still is a lot of work)? I'm an enterprise developer (JEE) so kerneldeveloping is new to me. Will check the links in your signature though :good:
[Fairphone 1] chrmhoffmann:
Sigh. I think that also the new kernel sources don't work. I can't get it to boot. http://pastebin.com/raw.php?i=4bv6fyWw

The ringbuffer and/or ram console are quite small, so I don't really get much output. Looks like some problem with the dsi/display.

ARRGGHHH...

Chris
[Fairphone 1] longjohn119:
I just don't understand the ChiCom's thinking here .... You have a small army of intelligent motivated developers willing and able to extend your code AND your hardware for free ..... and you just sh-- all over them? There is nothing going on inside a Mediatek processor that's unique, groundbreaking or proprietary that's worth protecting. I say that as someone who has been in the field of Industrial and Commercial Process Controls since 1997

It's like they don't really want to make money and I'm afraid they've picked up a bad habit that's plagued the US business community for decades

Penny wise and Dollar foolish .... Save a couple of pennies now and throw way several dollars in the future (For instance it is ALWAYS ALWAYS ALWAYS cheaper to mitigate Pollution at the source than it is to clean up the environmental and health degradation it causes, I've yet to find a single exception to this Rule and the ChiComs are going to learn it real quick the hard way in the very near future)

Can't they see why the Nexus 7 was such a hit? Can't they see how Google took a device that's Margin was so low it was obviously never meant to make real money but since it was so Open it was embraced by the WORLDWIDE community and became a money making best seller. Cripes the biggest downside to a Nexus 7 is that there are so many ROMs and Kernels out there it's hard to choose and takes a week or more of research to cull your way through them

My only conclusion that they are Thieves at heart and thus think everyone else is out to steal from them like the steal from others .... Another bad habit they picked up from US "Corporate-think" .... Or maybe they do such shoddy coding that they are embarrassed to have anyone see it ... nothing pisses off a so-called Professional more than a bunch of 'amateurs' laughing at them and showing them up ....

Plus like any Corporation it's not the better educated engineers and scientists that call the shots but the poorly educated MBA's who don't know a resistor from a capacitor and couldn't even fix a broken flashlight or change their own oil ....
[Fairphone 1] Entropy512:
Yup. This is why Oppo has done so well in the West compared to other Chinese manufacturers despite almost no international marketing efforts outside of social media - Instead of crapping on community developers, they embraced them and we became their evangelists.
[Fairphone 1] lupin3_20hot@hotmail.com:
A little bit desappointed

My first fairphone is about to arrive and I've been looking for sofware news for weeks. Disappointedly, I've found FairphoneOS is not being Open Source and customizable... Is it true my research conclusion?

Thanks in advance

Lupin
[Fairphone 1] fredflegel:
Ubuntu Phone and Fairphone

If have read this article on omgubuntu.co.uk http://www.omgubuntu.co.uk/2014/02/bq-aquaris-ubuntu-phone-specs and if i read this correctly, the Ubuntu Phone by manufacturer bq will use a MT6589 (without M). This is essentially the same chipset as the fairphone but with a higher clocked gpu. This should ease porting ubuntu for phones to Fairphone i guess. It will be interessting how (and if) Canonical publishes Ubuntufor that phone. It might actually include sources to help porting Ubuntu to Fairphone.

What do you think?
[Fairphone 1] JY-G3:
Well, and what do you think about Neo900: http://neo900.org/#features

Yes, I consider this could be considered spam; sorry for that.
[Fairphone 1] supersn0b:
Hi all,

anybody seen/tried this: gizmochina.com/2014/03/10/finally-android-4-4-kitkat-is-available-for-mediatek-mt6589-chipset

Could that be good news?
[Fairphone 1] superdragonpt:
What's new? ;)

Search right here on xda.

There are currently two cyanogenmod builds (CM 10.2 - jb 4.3) and (CM11 - KK 4.4) for the wiko stairway MT6589.

Check the miscellaneous android development forums ;)

Regards
[Fairphone 1] iZLeeP:
Hi Guys! Someone in xda pointed me to this site http://mobilesupport.lenovo.com/us/en which contains source codes for Lenovo phones running MTK chipsets. Since I'm not that familiar with source codes, can anyone have a look and verify if the files are indeed the complete source codes for said Lenovo phones.
[Fairphone 1] entr0:
build and boot a custom kernel

Hi all,

I was able to build and boot a custom kernel. The problem is that the Fairphone kernel sources are in fact not configured for the Fairphone.

The display configuration in mediatek/config/ahong89_wet_jb2/ProjectConfig.mk is obviously wrong. So I changed CUSTOM_KERNEL_LCM in this file to nt35516_qhd_dsi_cmd_ipsboe (one can guess this by looking at /proc/cmdline and browsing through mediatek/custom/common/kernel/lcm). There are many more CUSTOM_KERNEL_* settings in this file and I have no idea what to put there. Therefore I excluded as many MediaTek drivers as possible from my kernel build, just to increase the chances that it boots properly.

The kernel was building fine and so far I tried to put my custom kernel on a recovery image. And finally it boots! :) The recovery menu is (almost) usable, the only problem is that the volume up button is recognized as volume down and the volume down button does not work at all.

The bottom line is that the configuration for the Fairphone board is not included in the kernel source. There are just the ahong folders with some generic configuration and customized source code, but I would expect to see also corresponding Fairphone folders. (So parts of the source code customized for the Fairphone are most likely missing, too.) I would not consider the current kernel source as complete. Let's hope that the guys from Fairphone are able to get the complete sources soon. However, it should be possible to start some development with the current sources already.
[Fairphone 1] Vinnl:
Thanks for your work! So I guess the question [MENTION=5382171]joemier[/MENTION] could pass on would be: Could the display configuration for the Fairphone from mediatek/config/ahong89_wet_jb2/ProjectConfig.mk be included in the kernel sources?

I can imagine it being difficult to know what questions to pass on to the technical team and how to formulate them, so I think it'd be useful to state them explicitly.

(Or is [MENTION=1656095]benxda[/MENTION] still collecting them for Joe?)
[Fairphone 1] entr0:
OK, I'll give it a try. :)

The problem is not only the file ProjectConfig.mk. I think the following folders are missing:

mediatek/config/FP1

mediatek/custom/FP1

Of course, I don't know if the name of the folders would be FP1 or fairphone or whatever. There are only the ahong89_wet_jb2 folders, which seem to contain some generic template (or maybe are for a development board). Alternatively, it might be that the phone-specific files should actually be in ahong89_wet_jb2. Whatever is the case, either some folders are missing or it is not the kernel source for the Fairphone.

AFAIK makefiles like ProjectConfig.mk are also covered by the GPL. I think this is concrete evidence that the current kernel package does not comply with the GPL. Not to mention the issue with the volume buttons.

So the people at Fairphone should ask again for the kernel sources and point out the probable violation of the GPL.

If one of you is in direct contact with the person responsible for the kernel sources at Fairphone, then please pass on this information.
[Fairphone 1] tobwes:
Just so that this matter gets it's righteous attention in the correct thread as well: there has been a new release of source code. Can't post the link, but you will find it in the "Technical details" thread, p. 66. As far as I can say, it seems that the config has been released as well (at least the PackageConfig.mk in the ahong folder has been changed). Though, I can't try to build it because I don't have a fairphone myself (only a family member has one, but he's using it).

So I hope that this is a step forward and at least the kernel will compile and run properly. I know, that it is still a lot of work after that to get a custom rom, but I'm still dreaming ;)

Keep up your interest, I appreciate it very much! If I only knew how I could help, I would do so, but without a phone I don't know what to do...
[Fairphone 1] tobwes:
Hi,

here I'm gonna explain, how I managed to compile sources, although I'm not sure that they run, since I don't have a device for testing. Also, notice that I took three files from other mtk repositories (see [1] and [2]).

First, I followed the groundwork of fredflegel and _tmp from the technical details thread. I've put my complete work to a fork of benlorenz' fairphone repo. you can find that on github if you look for zaibotw / alps-fairphone-gpl along with all changes I've made.

After setting things up and hitting the same bumps as _tmp and fredflegel, I searched for the missing files on the internet. The search was successful. I found the file "stk3171/cust_alsps.c" on repo [1] and "bma250/cust_acc.c" on repo [2]. The missing lcm file was solved by changing the required driver in /mediatek/config/ahong89_wet_jb2/ProjectConfig.mk from "nt35516_qhd_dsi_cmd" to "nt35516_qhd_dsi_cmd_ipsboe" (see etr0's comments above). Since make still complained about the "nt35516_qhd_dsi_cmd", I had to comment out two lines containing this string in /mediatek/custom/common/kernel/lcm/mt65xx_lcm_list.c

For the "stk3171/cust_alsps.c" to work properly, I had to comment out "#include <alsps_cust.h>" there and instead use "#include <stk3171.h>".

In the "bma250/cust_acc.c" file I had to add these lines:

#ifdef MT6589
#include <mach/mt_pm_ldo.h>
#endif

I hope that I didn't forget any changes I've made. But anyway, you can get my current state of the source from the above mentioned repo zaibotw/alps-fairphone-gpl once it is finished uploading there.

Also, please notice that I added the files from the other devices just because they are from mediatek and have the same id. so that I'd guess they match with our missing files. :-/

Hope that this works. Please report back your experiences.

[1] GitHub bindassdost/BindassBoost_a110

[2] GitHub wiko-sources/cink-slim
[Fairphone 1] _tmp:
I successfully built a kernel with the ipsboe lcm and with stk3171 and bma250 disabled. But it wont boot, stays on the blue screen and reboots after a while. I tried it both as a recovery kernel and in a boot.img. I created the images with mkimage (from inside the source tree) and github: bgcngm/mtk-tools.

In the very short kmsg from the failing boot i get a spinlock lockup after 5 seconds.

I might try disabling a bunch of the custom mtk drivers next ...

[MENTION=5842791]entr0[/MENTION] is there something else that you did to get a booting kernel ?
[Fairphone 1] fredflegel:
I will try this!

Hi, i will try too build when i am back home next weekend. Maybe we get the missing files directly from Fairphone until then. Any chance [MENTION=5757561]_keesj[/MENTION]?

As they seem to be more active in the forum in recent times, there might be a chance they are already talking to Ahong/Mediatek again.

Thanks for your work so far! :cool:
[Fairphone 1] _tmp:
For anyone trying to build a kernel from the new sources, it seems the partition info struct (in mediatek/platform/mt6589/kernel/drivers/dum-char/partition_define.c ) got messed up in the update. This caused a very early boot failure because the size of the struct was only 20 instead of 22 as defined in partition_define.h.

I reverted to the one from before the update and compared with "cat /proc/dumchar_info". Only the start addresses are offset by the length of the preloader but this might be correct.

I pushed this change to my github (benlorenz).

With this kernel i could successfully boot a recovery image and create a user_data backup for testing purposes.

I will try to replace the kernel in the main bootimg next...
[Fairphone 1] _keesj:
Hi,

To get a better understanding of how the partition works I suggest starting to read/fix the wiki page here

https://github.com/keesj/alps-fairphone-gpl/wiki/MTKPartitionLayout.

Depending on the partition layout you will have a different amount of partitions. My guess is that one needs to run the perl script to generate the correct header and c files.
[Fairphone 1] _tmp:
Thanks for the information.

My first try with this script only gave 20 partitions (no FAT and no EBR2) but after a few tries looking at the log I found that setting the following

# sdcard will be a folder of /data
MTK_SHARED_SDCARD=no

in the project config (original value is yes) causes ptgen to generate the partition headers that fit with dumchar_info (and the ones from the old source package I used earlier).
[Fairphone 1] _tmp:
Another update:

With my latest changes i got a kernel which boots at least to the "Loading" logo on the display but does not show the bootanimation. But even better, I got access to adb and logcat and a lot of things seem to boot up correctly (e.g. modem, gps, audio). But it seems that the display driver fails to load:

I/SurfaceFlinger( 131): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
... some other logs ...
I/ServiceManager( 507): Waiting for service SurfaceFlinger...
E/IMGSRV ( 131): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 131): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 131): :0: PVRSRVConnect: Unable to open connection.

and these lines keep repeating ... and they do not appear in a normal boot.

I also get:

W/libEGL ( 131): eglInitialize(0x1) failed (EGL_BAD_ALLOC)

I compared the strings in the unpacked stock kernel with my custom kernel and the first one contains nt35516_qhd_dsi_cmd and the custom kernel contains only nt35516_qhd_dsi_cmd_ipsboe.

So I would claim that the ipsboe display is close enough for recovery but still not the correct display for OpenGL graphics.

[MENTION=5757561]_keesj[/MENTION] can you please try get the correct display settings for us, this should be in the folder 'mediatek/custom/common/kernel/lcm/nt35516_qhd_dsi_cmd/' ?
[Fairphone 1] chrmhoffmann:
Did you compile the kernel with this variable?

TARGET_BUILD_VARIANT=user

So when compiling do something like

TARGET_BUILD_VARIANT=user TARGET_PRODUCT=ahong89_wet_jb2 MTK_ROOT_CUSTOM=../mediatek/custom/ make -j8

Did you also update the kernel modules under /system/lib/modules?

Chris
[Fairphone 1] _tmp:
I had already copied the modules (and corrected the permissions) but it still didnt boot. Now with the build variant set it does boot, Thanks!

Most of sensors are still broken. Only the gyroscope works.

We should have accelerometer, gyroscope, magnetic field sensor and ambient light+proximity sensor.

In the new projectconfig they are the following:

bma250, mpu3050c, mmc3416 and stk3171

In the original kernel we do have strings (function names...) for exactly these but in my kernel they do not work, except for the gyroscope.

(I added the cust_* files as posted by [MENTION=5959355]tobwes[/MENTION] )

The sensor app shows different sensors (even on my kernel) and I have no idea where those names are coming from: bma050, mpu3050c, bmm050 and cm36283.
[Fairphone 1] chrmhoffmann:
_top have a look at the projectconfig.mk. I think the changes are maybe just wrong. Try to use the older settings for bma050 etc. Does the touchscreen work?