yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] _tmp:
Apart from the sensors everything seems to be fine. Touchscreen works, wifi works, modem too (data connection, phone).

I tried the other settings and the acceleration sensor works with this setting (except that the axes are switched) but bma050 and bma250 is not that much of a difference.

The bmm050 magnetic sensor and the cm36283 alsps do not seem to work.
[Fairphone 1] tobwes:
To get the axes right it might be possible just to permutate the axes in the source file "bma250.c". They are indexed by the constants BMA250_AXIS_X, BMA250_AXIS_Y and BMA250_AXIS_Z right at the beginning of that file.

Well, and in the ProjectConfig.mk there is an option for MTK_AUTO_DETECT_MAGNETOMETER. Maybe this can help, although I don't know if you need to enable more drivers in the CUSTOM_KERNEL_MAGNETOMETER field then and also I don't know if this would work with any subset of drivers or just with those which have a suffix _AUTO in their directory paths.
[Fairphone 1] _tmp:
It seems I got the sensors working as well, acceleration, magnetic and ambient light + proximity. (gyro was already fine)

The magnetic sensor started working after I fixed the other two, maybe the wrong values somehow blocked it or a cleanup of some directories in my build-tree helped.

They needed some slightly different parameters:

i2c_num=3

changed the direction of the acceleration sensor to 3

changed the firlen of the acceleration sensor to 0

also changed a few values in the alsps

I found the correct/working values by going through a hexdump of the original kernel and comparing it to some debugging of the custom one...
[Fairphone 1] _tmp:
After using it for a day I found that the touchscreen (in combination with the display) has some serious problems: If I open an app with too much white background I get random touches all over the screen even when I'm not touching the phone at all.

For example after opening a pdf file with acrobat reader it scrolls and zooms around without me doing anything, sometimes also hits back or menue. Also Google Maps is unusable.

In the Engineer Mode App in the "Line Verification" the phone quickly draws lines all over the screen by itself. In "Point Verification" new points keep appearing with a high error value.

On the other hand, the tests on dark background (multitouch test, handwriting test) work. But I do have the impression that I get more small lines instead of points for touches with the custom kernel.

EDIT:

I added a few images to illustrate the random lines. The screenshots were taken a few seconds apart via adb with me not touching the at all!
[Fairphone 1] chrmhoffmann:
For me it doesn't work. I tried your kernel sources, too, from https://github.com/benlorenz/alps-fairphone-gpl

But I still get this error here on boot. Seems display related.

http://pastebin.com/raw.php?i=tT2GKSsa

Chris
[Fairphone 1] hanzano:
Reminds me a bit of this issue: http://xdaforums.com/showthread.php?t=2647294
[Fairphone 1] _tmp:
I just checked out my repo into a new and clean folder, ran the make command from the README, created the boot.img, dd it to /dev/bootimg and copied the modules. It boots fine.

Maybe there something different in the img creation ?

I'm using the following:

mediatek/build/tools/mkimage ./zImage KERNEL > ./zImage.img
./repack-MT65xx_mine.pl -boot zImage.img origboot.img-ramdisk.cpio.gz boot.img

I have slightly modified the unpack and repack scripts from https://github.com/bgcngm/mtk-tools so that they dont unpack the ramdisk and origboot.img-ramdisk.cpio.gz is what I extracted from the original boot.img.

It looks like the display panic appears after the reboot is already initiated, from the "Exception stack" at the beginning I think there was another panic earlier. (And I think I have seen a some panic during reboot once too)

I'll do some more testing and post some screenshots later.
[Fairphone 1] Unrelashade:
About the random touches issue: I remember people posting about random touches while charging the phone. So maybe not having the phone connected will solve that problem and show that this is a hardware problem.

Hope this helps

also, maybe it's easier to collaborate on the wiki and collect information and compiling steps/ manuals?

http://xdaforums.com/wiki/Fairphone_Fairphone
[Fairphone 1] zelendel:
IT may not be hardware. As on one of my devices we are working on a software bug that messes up the touch imput when the device is pluged in. We know its software as it was not an issue before. So your issue may also be software and not hardware.
[Fairphone 1] tobwes:
I am home for just about two weeks and since there is a re-partitioning of the phone scheduled in the next update I am willing to test your current code. However, this will be the first time that i try to use a custom (self built) kernel. The most adventurous experience I have so far is installing a cyanogen mod on a galaxy sII (which is quite easy), so a small wiki entry regarding the procedure would actually help me a lot and safe me a lot of time.

Also I still need to figure out how it will be best to backup the phone (especially apps like whatsapp and textsecure).

If someone has the time to give short advice that would highly be appreciated (with testing reports ;) ), otherwise I will have to spent more time on research on the internet.
[Fairphone 1] _tmp:
Im quite sure it is a software problem. It only happens with my custom kernel, but both when plugged and unplugged.

Moreover, I am using a different display driver than the stock kernel (_ipsboe is not present in the strings of the original kernel) and it happens only when the screen is mostly white.

So I still hope for the correct display driver and maybe we need better touch calibration values.
[Fairphone 1] superdragonpt:
Hi

This issue isn't related with this kernel, but with MTK API, it happens on several MTK devices (i own 5 MTK devices, same isue on all of them)

Connect your charger, then disconnect and connect again, should be fine now...

The first time you connect the charger you'll notice that all cores will be at full speed (avoiding the IDLE )

Ontopic:

About the sourcecode, there's a lot to merge and fix on the stock sources (this is starting to be anoying on all my kernel MTK projects).

You should REALLY disable the MTK debug functions on mediatek/config/MT../ .... / platform

Not only it will reduce your compiled zImage (+- less 300KB) and it should and will avoid several issues on Booting the kernel

I really can't spent more time on this, i was doing an favour to an friend of mine, still busy weith two other MTK kernels projects (MT6577 zte v970 and MT6582 Wiko darkmoon)

Good Luck ;)

Regards

EDIT:

I noticed that the OEM talked about some issues regarding Reparticioning (I think there's two hardware revisions ???)

Thats hardcoded on the kernel under ../mediatek/custom/ Project/common on the partition.define.h

Example:

https://github.com/dragonpt/ZTE_v970_Kernel/tree/master/mediatek/custom/ztev970/common

Regards
[Fairphone 1] _keesj:
ahong89_wet_jb2 is the machine named used during the build so no missing config here.
[Fairphone 1] entr0:
I am very excited to see that there is a new kernel source package (v3) and from the reports above it seems that it almost works. Many thanks to the Fairphone team for being so persistent on this subject, and to everyone helping to make a custom kernel!

Ok, so the config was not missing, it was simply the wrong one :) The new sources contain many changes in ProjectConfig.mk and mediatek/custom/ahong89_wet_jb2/kernel/dct/dct/. The latter contains files describing how the board is wired.

Notice that there is a copy of ProjectConfig.mk on the Fairphone ROM, it is in the folder /system/data/misc. The CUSTOM_KERNEL settings there completely agree with the ones in the current kernel package. This is another indication that the correct lcm driver might still be missing.

From above discussion, I think up to now the issues with the current kernel sources are:

need fix for: mediatek/platform/mt6589/kernel/drivers/dum-char/partition_define.c

probably missing folder mediatek/custom/common/kernel/lcm/nt35516_qhd_dsi_cmd/ and/or corresponding changes to mediatek/custom/common/kernel/lcm/mt65xx_lcm_list.c

missing file: mediatek/custom/ahong89_wet_jb2/kernel/accelerometer/bma250/cust_acc.c

missing file: mediatek/custom/ahong89_wet_jb2/kernel/alsps/stk3171/cust_alsps.c

maybe an additional issue with the touchpanel driver/configuration

Correct me if I overlooked something. It would be great if the Fariphone team can ask for another, hopefully 100% complete, kernel package.

Just a wild guess on the touchpanel issue: maybe one can try ft5316_driver.c.bak instead of ft5316_driver.c for the touchpanel driver and see if it works better? I just had a quick look, but there might be omissions related to calibration in the current file.

Unfortunately, I am rather busy these days and have no time to experiment with the new sources right away, but I will try ASAP!
[Fairphone 1] _tmp:
A few comments on these issues:

The partition files in the original 1.3 sources seem like they corresponds to after the partition upgrade (no fat, bigger cache) but I was able to generate correct files with the included ptgen script after setting MTK_SHARED_SDCARD=no. [1]

There are working cust_alsps.c cust_acc.c in my github, I got them from other repositories and the parameters are adjusted to the ones extracted from the stock kernel. All those hw sensors work fine and give reasonable values in the the kernel I compiled. [1]

I think we really need that display file (and having a correct display might also fix the touch issue as somehow the brightness has an influence ...)

Moreover, a 1.6 source package would be good.

All parameters for the touch panel I could find so far seem identical between the files and the stock kernel.

I had a look at those files and i think the .bak is really a backup and the file was split up into several source files. Many parts that are not in the .c anymore can be found in ft6x06_ex_fun.{c,h}

[1] see here
[Fairphone 1] _keesj:
We got a new patch containing *only the LCM changes* I haven't had time to look into it.

http://www.fairphone.com/downloads/software/fp1_source_code/GPL_patch_20140731.tar.gz
[Fairphone 1] _tmp:
Awesome, thanks. The new display driver is correct, works and even fixes the issue with random touches! I pushed the driver to my github.

I will do some more testing of the custom kernel soon and try to start removing some mtk debugging stuff ...
[Fairphone 1] superdragonpt:
You can start by :

removing KALLSYMS stuff

Clean main Makefile

Clean *junk* declarations on some mtk drivers under platform/ custom

Try to compile with 4.7+ toolchain ( see if it builts ) usually some fixs are needed on mtk kernels.

( check WiFi modules under /platform)

The old ( stock) toolchain used my mtk ( arm eabi 4.6) is really outdated'...

Regards ;)
[Fairphone 1] step21:
Re: Release of driver sources ...

If anyone is still interested in this ... you could try to contact gpl-violations.org on their mailing list, to check what they think.

However personally, I don't have too much hope ...
[Fairphone 1] zelendel:
Contacting them won't do any good. As they are in China they are not held to alot of laws
[Fairphone 1] step21:
While I know what you mean, this is not necessarily true. I know people who do enforcement of licenses, including alternative licenses such as the GPL, and they have prevailed most of the time. Often just asking in a professional manner helps. At this point it is for example not clear to me, were they even asked? Who asked, and how?

In case they really don't seem to care, next steps can be thought about - such as - does someone know(or is) a kernel developer that wants to pursue gpl enforcement? In case this is a problem, as I suggested, someone should talk to gpl-violations.org first. This is of course not a guarantee, but they can advise more precisely.
[Fairphone 1] zelendel:
We have contacted them on a few oem that don't follow the gpl. Take the MIUI OEM they refuse to release the kernel source for their devices and when asked about it they say flat out that they don't have to follow it as China does that enforce Any copyright laws.
[Fairphone 1] step21:
I didn't say it wasn't a problem with a lot of manufacturers. It is. However I wanted to know specifically if you asked the company resposible for the fairphone chip. Is that the same one that did MIUI? Granted, certain countries are a bit selective in enforcing copyright, but this doesn't mean they don't do it at all. It also doesn't really matter what they say - ofc it's probably easier for them not to do it and try to get away with it, they still have to do it. At the very least, however, they would start to care if someone got an injunction and it threatened their sales or other relationships abroad. (assuming they export most of their stuff) I'm not saying that it is easy, but that is the way to go, if talking (specifically to the relevant manufacturer, about this phone/chipset, with documented communication) didn't work.
[Fairphone 1] zelendel:
Your missing the point. OEM out of china don't have to do anything. We have been down this road with a few oem like micromax. They import their devices from china and are not provided the kernel source so they can't provide it. They have been reported a dozen times but due to the laws in that country there is nothing they will do to change it. Search around. There are dozens of threads about it. You have to remember that not every one is held to the same laws as we are
[Fairphone 1] Unrelashade:
Something I use to wonder about: Is it not forbidden to cooperate with a company that breaks the law? Would that be too complicated?
[Fairphone 1] superdragonpt:
Exactly

Also you guys should know, that, most MTK Vendors don't get the sourcecode for their devices.

Instead they get an pre-compiled binary .

And China doesn't comply with GPL and/ or patents.

@op

If you need any help with the mtk kernel, drop me an PM.

Regards
[Fairphone 1] _keesj:
If there are more problems with the GPL/kernel release please explain the problem. the latset drop will needs some cleanup but looks complete to me(in terms of kernel)
[Fairphone 1] jreg2k:
Hi,

I am new to this forum but I really want to help developing a custom ROM for fairphone.

I have some questions :

How to compile the the kernel you are talking about ?

Is it possible to install now a custom ROM ?

Thanks for your answers.

Regards.
[Fairphone 1] Unrelashade:
Hello, nice to see your interest. Just search for this, for example

https://www.google.com/search?q=begin+ROM+development+android&gws_rd=ssl

I'm interested myself, but can't do it as of now. Maybe open up a new thread where you write about what you did and how and what your problems are, etc. I'm sure you'll get a lot of help. You can also ask in other sections of the xda forums. You might also use the fairphone article of the xda wiki to explain for others what is needed: http://xdaforums.com/wiki/Fairphone_Fairphone

Good luck! :)
[Fairphone 1] _keesj:
I gathered this information into a wiki page here. https://github.com/keesj/alps-fairphone-gpl/wiki/Building the instructions are not complete yet (copying of the kernel modules is for example missing)

---------- Post added at 11:17 AM ---------- Previous post was at 10:50 AM ----------

I requested the missing files and these where provided here:

http://www.fairphone.com/downloads/software/fp1_source_code/GPL_patch_20140825.tar.gz

the git repo https://github.com/keesj/alps-fairphone-gpl also contains this change
[Fairphone 1] _keesj:
Thanks to fixes inspired by [MENTION=5959593]_tmp[/MENTION]'s work the https://github.com/keesj/alps-fairphone-gpl repository now builds a working kernel

Find the instrutions here https://github.com/keesj/alps-fairphone-gpl/wiki/Building

enjoy
[Fairphone 1] chrmhoffmann:
Hi,

Thanks for your effort.

The wiki talks about fastboot. How do I enter fastboot mode on the device?

Update: I have 1.6 FP OS.

Chris

PS: I still can't make it work for CWM recovery, but it might be my fault.
[Fairphone 1] jreg2k:
OK I will do that.

Thanks.
[Fairphone 1] _keesj:
Fastboot requires replacing the little kernel (kl) that can be downloaded from the faitphone websiite. Ather that

booting with volume up+power will present you with a choice menu to boot into normal, recovery or fastboot mode.
[Fairphone 1] sycoso:
Where do I have to flash the lk.bin to? And should I use the image from the FP1 or the FP1U zip if I have a first badge phone with fuse layout?

(sorry if that's too off topic)
[Fairphone 1] haffenloher:
If you used the "storage upgrader", you will have to use the FP1U image. The other one also has "1G13G" in its file name, I guess that's a hint it uses the old partition scheme with two internal storage partitions, one 1 GB and one 13 GB in size :)
[Fairphone 1] sycoso:
I thought that the image might not be compatible since there's an other SoC in the FP1U. I couldn't think of a reason why the lk should know about the different partition layout and was confused because they have different hashes.
[Fairphone 1] haffenloher:
I should have mentioned that in my first post: I have the FP1U image up and running on my first batch phone! Installing the FP1 image didn't work because of the new partition layout.
[Fairphone 1] chrmhoffmann:
I got it booting. Thanks. I made some stupid mistake.

Now go over to the original android development thread and test a bit my kitkat version.

Chris
[Fairphone 1] superdragonpt:
Thanks

Compilation is good now.

You can costumize the build script to be more user friendly...

...without the need of exporting vars on terminal, and you can add auto patch the zImage header into the build script also..

Regards
[Fairphone 1] shooter_92:
Useful?

Does anybody know if the online-petition are useful?

There are ca. 50'000 FP's sold. The Subscriptions ATM are 1,660.

100'000 are needed. This means that 3'012'048 FP's have to be sold

to make this petition work?!?

Hopeful, shooter
[Fairphone 1] Unrelashade:
I can't tell you if such petitions work, but we have the sourcecode now from mediatek through the Fairphone people :) Check out the development forums
[Fairphone 1] k_akos:
The makers of FP1 acquired all the licences and drives. Just search for: Long-term software support for Fairphone 1
[Fairphone 1] z3ntu:
Quote from the Fairphone Forum:

So probably no custom rom support... :(
[Fairphone 1] Jisifus:
https://www.reddit.com/r/Android/comments/4uobie/team_mad_mediatek_android_developers_brings_cm/

Does this help anyone? It looks like source codes are out.

https://en.wikipedia.org/wiki/List_of_devices_using_Mediatek_SoCs#MT6752

That's a list of devices running these SoCs. The 2014 Fairphone is there too.

Is there any way at all we'll ever get a stable CM11 release for this phone?
[Fairphone 1] zelendel:
That is only part of it. You still need device trees. Those sources are just for those devices.

Also if you are looking for stable CM is not gonna be it.
[Android Q&A, Help & Troubleshooting] dawkun:
Welcome, I am newbie in android (generaly in smartphones)

I bought Sharp SH-06E from Japan (Docomo) and i would like to unlock all it's functions and add more.

I am specially interested in root, unlock bootloader and custom rom (everything)

As far as i found it's impossible, but maybe someone know how to do that and would like to share some informations. I heard that on Japanese forums they know how to do it, anyone from Japan?

Device info:

Build number 01.00.07

Model number SH-06E

Android version 4.2.2

Baseband version 1.00

Kernel version 3.4.0 build@Sharp #2 Thy Sep 19 03:04:19 JST 2013

I tried to root it with my friend with "kingo android root" and i downloaded some Japanese pack named "SH06 root kit v25" but it's in Japanese language and i can't understand it at all.

Kingo couldn't see my phone (yes i turned on usb debugging)

if anyone knows sth, please help

Thank you v m

David from Poland
[Android Q&A, Help & Troubleshooting] Hree:
See here: there are two kits to root it (in English language) (I for myself used the "rooted tools version" and it functioned well (there was only a loop during the first or second reboot, I powered the phone of and after starting the phone everything was o.k. and went on with the root kit)):webside: sharp.cheeseus.org/index.php?page=Applications

For changing the language you can use some apps from the play store after rooting, (with the app from sightidea you can change as well without rooting but using adb)

I think your phone is unlocked, if not there is an unlock kit too
[Android Q&A, Help & Troubleshooting] joshua.maxell:
Hi,

I used sh06e_root_kit_v026 and usb_driver_SHARP_r8.5. Everything looks ok but I don't know if I can upgrade the system for Kitkat and how to do it.
[LG Optimus 4X HD] konzakul:
Hi,

is there any mod like this one

http://xdaforums.com/showthread.php?t=2091959

for our 4X HD? Or a KitKat ROM which brings this feature?

Or any other possibility to automatically record a call in good quality?

The free Apps I found either didnt work or only recorded my own voice..

thx
[JAM, MDA Compact, S100 General] klenovsky:
when is th Backup battery used and for what?

thanks :oops:
[JAM, MDA Compact, S100 General] hanmin:
the magician (and many others older model) doesn't have persistent memory, it needs a battery to keep its contents. The backup battery will not start your phone, but it will keep your data safe for a few days (after your main battery goes dead), giving you enough time to charge your battery.
[JAM, MDA Compact, S100 General] klenovsky:
Super!

thanks for the info!

Cheers,

Klenovsky
[JAM, MDA Compact, S100 General] HyperMalac:
Have you tried how long the backup battery lasts? Because once my main battery exhausted, and after 30 minutes I put on the charger, and saw the backup battery is at 80 %... So I think the backup battery lasts for a half day, or is it depends on what background porgrams running, or what?
[JAM, MDA Compact, S100 General] sajib:
[/quote]Have you tried how long the backup battery lasts? Because once my main battery exhausted, and after 30 minutes I put on the charger, and saw the backup battery is at 80 %... So I think the backup battery lasts for a half day, or is it depends on what background porgrams running, or what?[/quote]

Jam and all other wm2003 device have two type of backup battary option....

1)Which is situated in jam motherboard...a 3v battery...

if u remove ur man battery then it will keep power on ram for 30-40 min at most....after that a hard reset...

2)jam keep a portion of main battery for backup reason...that is if even ur main battery reach 0%...then this backup portion of main battery will keep power to ram for nearly 72hours (3Days)...if ths portion also reach to 0% then the 1st option will work for 40 min..

i think this will clear any quary abt backup battery of wm2003 device..

PS:new wm5 devices doesnt have any backup batter nor the 1st one nor do the 2nd one...as this is a persistent memory based os...thats is one another reson thats why wm5 devices have better battery performance then of wm2003..