yashsingh1/xdaforums huggingface dataset:
[Android General] eazypop:
Hello,

I just bought a p6000 (not a pro) and i'm having problems connecting to any wifi connection...

Already tried using wifi fixer apps but all of them failed.

Running lollipop and so maybe this is a problem (which i doubt...), so maybe changing the ROM and or kernel will help?

It's probably the wifi hardware (or firmware?) which is broken :S

I'm a super noob with these sorts of things, so i actually have no idea what a kernel is and actually neither really what a ROM is.

In any case; what do i do and/or how should i resolve this (how to install a new rom or kernel or how to fix the wifi)?

Thanks in advance :)

Kobie
[Android General] GoJo ^^:
I switched from 40mhz to 20mhz in router settings & that was it.
[Android General] losiek95:
CWM p6000

I was wondering if this CWM for p6000-02 will work with my p6000-01?

http://xdaforums.com/android/development/elephone-p6000-mtk6732-64bit-sp-flash-t3007070
[Android General] HypoTurtle:
Yes it'll work. The only thing you to check is if it's for KK or LP the -01/-02 doesn't matter
[Android General] GoJo ^^:
Is the P6000 compatible with HDMI MHL adapter? Maybe particular one (there are different versions it seems..)?
[Android General] GoJo ^^:
It seems quite dead around here but i'll still ask : Anyone tried encryption with modstock v3 rom (5.0)?

Never did encrypt any droid phone before, wanna try but need to know : is it easy to decrypt..? Please give details ;)
[Android General] GoJo ^^:
Hmm well i think i tried it on the 5.1 roms and after reboot it totally crashed (data partition corrupted). Guess 5.0 would be same..
[Android General] GoJo ^^:
Anyone still coming around? I'm having the issue of endless boot animation. Generally, deleting caches will fix, however it doesn't now. I just can't understand what's in this damn phone, i'm having so strange issues i never had with any others..!
[Android General] andrei80:
Install a stock firmware, including Blaster 2 stock, they just work, no headache
[Android General] GoJo ^^:
Actually i found out that the modstock 5.0 rom (which i've been using for months, the best!) was updated from v3 to v4 and then v5 in the end of 2015!

Nobody seems to be aware of that? Found that out directly on 4pda.ru (with translator of course), i can tell many little annoyance were corrected!

However i'm getting little issues that i'm trying to sort out now. If you're interested, i can post the link (not sure i'm allowed though)..
[Android General] :
Mystory recently released Cm12.1 and some other Cm12.1 rom that works really good.

Check it out in bbs.elephone.hk
[Android General] andrei80:
I've tried almost all roms. All had little or big annoyances. Stock roms just work, especially with the help of xposed+ gravity. At some point I've decided that I need my phone to not annoy me and got back to stock. My last firmware was Blaster2 lollipop and it worked flawlessly. I am selling my phone,btw, already using a Huawei P8lite for about 1 week, and happy with it. Benchmarks are generally worse, but user experience is much better.

I still think all the modders did awesome jobs trying to improve a fast but flawed phone and thank them all.
[Android General] GoJo ^^:
Yeah, indeed thanks to them!!

Always quote my messages so I get notified quickly!

---------- Post added at 12:13 AM ---------- Previous post was at 12:05 AM ----------

TWRP been updated by the way?

Always quote my messages so I get notified quickly!
[Android General] HypoTurtle:
Is there a new TWRP version? There should be a 2.8.7.0 build and I believe thats the latest TWRP build.
[Android General] GoJo ^^:
The one that came out months ago, right? Anyways, tried modstock v5 as well as bliss: i think I just wanna stay on first one for some more time..

However I have reboot issue on both, caused by xposed: posted on 4pda but not sure they'll be able to help, perhaps you know?

When I reboot, it just spin forever.. I have to force reboot (long press power) multiple times, not sure why its so random..

---------- Post added at 03:44 AM ---------- Previous post was at 03:22 AM ----------

---------- Post added at 03:45 AM ---------- Previous post was at 03:44 AM ----------

The other issue I got.. My apps are actually taking 4gb at least..!

PS: sorry for the color tint, mistake!
[Android General] GoJo ^^:
Downloaded & (cleanly) installed the just5 blaster 5.1.1 rom : you told me it was all good however right after install i go in settings to change some quick settings and when i try to add one, settings crash..!!! Tried reinstall rom but same. I don't think you missed that..?
[Android General] nemo232:
This setting doesn't work. And another bug is, that when brightness is set to automatic or minimum then screen doesn't go on. But I set it manually and it worked. But ROM is very good.

Odoslané z Elephone P6000 pomocou Tapatalku
[Android General] GoJo ^^:
I (re)installed Bliss Pop rom (same as BLASTER but corrected and more tweaks), it is AMAZING but.. I have a mobile data network issue, it shows a ! If I select anything else than 2G. Yet SIM slot 1 is supposed to work..?
[Android General] :
If I remember correctly it is the bug that has been already reported, and by reading few of the recommended comments, I don't think we would be having this conversation.. Maybe I am wrong here.. Haven't been there for some time, so it might not be a recommended post..

As for Blisspop, I will be talking from my personal experience with it.. It is good, but most of the features atleast for me are useless, It got hard to use after some time, and laggier than Cm12.1, but it is also coming from someone who would rather like Aosp 5.1.1 than Cm12.1

That's all for today.. Have a good night :)
[Android General] bigrammy:
Please buy a iPhone! :crying:
[Android General] :
That Overpriced mini Samsung? You must really hate [MENTION=4365424]goja[/MENTION] if you want him to buy an Iphone.
[Android General] GoJo ^^:
I hope it's just me xD Anyways, I guess it was one thing among those hundreds to tick I forgot to tick -.-
[Android General] nlooooo:
Anyone tried EleFlash app from Elephone site? I gives 2 roms to download, stock 20150611 and VIBE 2.5.
[Android General] longo213:
Do not use it for upgrade from KK to LP.
[Android General] nlooooo:
I'm already on LP. So it works fine?
[Android General] GoJo ^^:
Anyone got a bug on bliss rom which is phone always boot in priority mode..? Otherwise, is it supposed to be possible to restore a nandroid from a p6000 to another p6000? It ends with "tar for error 255" or something like that during data restore..
[Android General] Lefti1511:
5.1 OTA Malware

Hello,

i have a OTA update to 5.1 and now i have Malware on my P6000 Pro. There was install apps without me, in Browser there will open sites independent.

At this time the Handy did'nt have root and i can't install an other rom. Is there help anywhere?

Sorry for my bad english.

Thanks
[Android General] longo213:
As far I know there was no official update to 5.1.
[Android General] Lefti1511:
:confused: but i has nothing install out there. there was a message to install a software update and nothing else, i have don't install any other app at this time :crying::(
[Android General] HypoTurtle:
It's a different device, you might get some help here - P6000 Pro.
[Android General] GoJo ^^:
Link won't open in tapatalk
[Android General] Lefti1511:
Sorry, Read first, then ask! :eek::D
[Android General] gsser:
İ have c5 ultra e5553. It just uses same cpu as other devices. Mt6752 64bit. I wonder which one should i flash from recovery or what should i do to port any of these roms(especially miui)?

Tx
[Android General] bigrammy:
You would be better requesting on the P7000 thread as that device is a closer match and for Miui you should make a request here http://miuipro.ru/roms/ with links to the sony kernel source etc
[Android General] arungpalakka88:
guide porting

bro,..please share guide porting mt6753 with same mt6753??
[Android General] HypoTurtle:
I believe with the vast majority of these, just switching the kernel (within the boot.img, or sometimes just whole boot.img) resulted in a ROM that would at least boot, obviously with something not working and needing to be fixed.

So I would start with that and work backwards.
[Android General] HypoTurtle:
And alter the boot.img I assume. (kernel switch and .rc files)
[Android General] bigrammy:
Hi and welcome to xda bro :highfive:

Yes I noticed you used archikitchen :cool:

I worked with archi to get our MTK SoC supported ;)

Good job on the zopo port it seems to work just fine Thanks :good:
[Android General] Xabadou:
The port of Ulefone Be Pro works too, but button home is missing and system only recognize external SD.

Patching boot.img maybe fix the problem, but I not tried yet.

---------- Post added at 11:08 PM ---------- Previous post was at 10:59 PM ----------

Another possible devices to port are ECOO E04 and Bluboo X6.
[Android General] HypoTurtle:
Ulefone is AOSP so not sure how useful a port would be...

Regardless removing /system/usr/keylayout/mtk-tpd.kl was the home button fix for flyme; it also seems to act differently at different dpi.

ECOO E04 and Bluboo (X6,X7,X8,X9) are all AOSP as well - but I've added them anyway.
[Android General] xenonism:
I found a link for Lollipop Beta 3 on Facebook. Apparently it was posted on the official forum, but the thread has now been removed. I am downloading and sharing the link just in case, but I don't know anything more than this.

P6000 Lollipop Beta 3 ROM

Edit: apparently it was just a broken link, the release is in the first post of the usual thread. I'll leave the link here for convenience, anyway.
[Android General] bigrammy:
Oppo Port

Hi [MENTION=4056517]HypoTurtle[/MENTION],

Just to let you know as requested I managed to get the Oppo Port booted but needs lots more work to get everything working :laugh:

[IMG="Oppo Port"]http://i.imgur.com/peX6hG0l.png?1[/IMG]

Some More Screenies
[Android General] HypoTurtle:
Lollipop Beta 3

Thanks [MENTION=3356343]xenonism[/MENTION] - Beta3 released a few days earlier than expected. Just ran a quick comparison against Beta2 with WinMerge - the differing files are:

preloader - seems to be just the build date changed - and a couple lines added to the end.

boot.img/recovery.img - appears to have a newly compiled kernel - ramdisk remains the same.

logo.bin - altered a bit

custom.img - is now being used - was empty with beta2

Installs 6 apps (5 of which can be disabled without any noticable ill effect);

The apps are a Chinese appstore (WoStore_1280.apk); (Wo3G.apk - browser bookmark), a mail client(AIMail.apk) and unicomClient.apk both of which crash.

The other apk that can be disabled is OperatorPlugin.apk.

Fwkplugin.apk can't be disabled.​

trustzone.bin - minor changes (4 lines)

and obviously system.img has been changed

scatter.txt is the same as beta2 thankfully so no problems with keeping userdata.

What's been fixed => the major bug with Beta2 was the SMS crash - this has been fixed

From the little I know about MTK developmemt and the problems developers had in the past - the main problem was with the dual-sim support as how MTK implemented this was keep closed-source, with 5.1 dual-sim support has been added to AOSP and with the first devices getting 5.1 (out-of-the-box) being the MTK run Android One devices I can't see it being too long before we have it as well.
[Android General] bayad:
Thank you for this information Master Bigrammy and for all your efforts. You will make many happy if you can port this ROM on our P6000 :fingers-crossed:

Just one question: the Arabic language is it present in this ROM ?
[Android General] bigrammy:
It needs a lot of work before it becomes usable but at least it boots :good:

There is no Arabic Language but I am sure this could be added from some other color OS V2 ROM that's an international version :fingers-crossed:
[Android General] bayad:
We look forward to your work Master. DON'T GIVE UP !!! :highfive::fingers-crossed:
[Android General] HypoTurtle:
MIUI Port by [MENTION=5593006]z0rgent[/MENTION] ; http://4pda.ru/forum/index.php?showtopic=628028&view=findpost&p=38623428

Main problem that needs to be fixed is the sim detection - any suggestions welcome.
[Android General] Levered:
on my phones jiayu s3 already get this rom this weeks, you can see this rom later.
[Android General] bigrammy:
Thanks bro :highfive:

I have not had much chance to work on this ROM due to working on the recovery. :rolleyes:

Have you got the sims detecting and does the Jiayu S3 have a custom partition :confused:
[Android General] HypoTurtle:
Yea I did spot that when I made the list on #54 but feel it would be a bit overkill detailing all the ports for 6732/6752, so tried to locate the original base ROM itself. I figured porting would be best done from the original ROM from the developer; if possible.

Was the G3 port from the Oppo U3 as well? How about the LeWa OS? Alcatel/TLC was the best I could come up with.
[Android General] Levered:
all works, just only a few bugs has detect like gesture don't work.

4G also working fine.
[Android General] bigrammy:
Thanks for the info bro :highfive:

I look forward to porting it when I have finished with the Android L recovery :crying:
[Android General] xenonism:
I got back to my pet obesssion of getting the notification light to work as it should, or as it used to work in V8.3 if you prefer. ;)

I found that in V8.3, the custom property ro.notification.breath appears to be unset to the system, even though it is set to yes in custom.prop. In V8.4, the property is read from custom.prop (at least if the value is "yes"), and the phone's beahaviour changes accordingly.

So far, I have found two references to the property in the source code of Services.odex, one relates to notifications and one to battery status indication.

The former makes more sense (to me, at least), in that it changes the notification behaviour between blinking and breathing. In practice, if you unset the property in custom.prop, notifications will make the light blink and not breathe (which is what I wanted). Note that even if you set the property to "no" in custom.prop, the system seems to read it as unset, but since the function in the sources defaults to "no", the result is the same. :good:

The latter reference is stranger. Apparently, when ro.notification.breath is set to "no" (or unset, as above), the battery charge level to be considered "full" is lowered from 100 to 90. This doesn't make much sense to me, both in absolute terms and in relation to the property. :confused: In any case, as one might logically expect, this doesn't affect the behaviour of the light while charging: in other words, whatever the value of ro.notification.breath, in V8.4 the light stays on while charging instead of breathing like in V8.3. I will try to figure this out and post any worthwhile updates.
[Android General] bayad:
A new ROM has just made its appearance : Elephone P6000 01 CM12 a1 (http://pan.baidu.com/s/1m6E2U). If a courageous wants to test it... :D
[Android General] jorjolo69:
Let's go [emoji2] [emoji2]
[Android General] bayad:
Looking forward to reading your feedback :)
[Android General] bigrammy:
CM12 Quick Report

Super Quick Test carried out

No SIM detection :crying:

No Bluetooth :crying:

No Sound from the Phone speaker or headset :crying:

Wifi works :good:

Other than that seems Awesome :good:

I love the look and feel CM12 so I hope we can get this fixed :fingers-crossed:

My Oppo port has the exact same problems :eek:

If anyone has the secret formula let us all know :laugh:
[Android General] greekfragma:
Wifi module most of the time is included on generic drivers because there not many companies making chips so the vendor list with drivers is specific and maybe implemented on kernel source code.

But for other devices like Sim card module, BT, Speaker we need the kernel drivers from Elephone or someone to disassemble our P6000 to pieces to check chip ID's so we can start searching for drivers :)
[Android General] Xabadou:
Port Asus X002

Last nigth I tried the port of Asus X002.

Works all fine except camera and flashligth.

The rom is only english and chinesse.

If anyone is interested , I can upload the rom to a server.

I have also tried the asus modem in miui rom.

The sim is detected but does not connect to the mobile network.
[Android General] HypoTurtle:
Have you tried the 5.0 yet? I don't see too much difference between this and AOSP 5.0 and most of the issues with CM12 aren't there.

I dirty flashed CM12 over 5.0V3; just installed system and boot as they were the only things that were changed (needed to clear some app data after to stop FCs). What I've noticed:

Boot.img is a normal boot.img (no kernel/ramdisk header); kernel starts at 800 instead of 200 later at a00 - haven't checked if the kitchen can (un)pack boot.img and leave it bootable yet.

Sim card seems to be an issue with most CM12 ROMs (just google CM12 sim empty).

Antutu cuts out at ~75% - perhaps a missing lib.

No MTK engineering mode (app hasn't been included).
[Android General] bayad:
I would gladly test it but as I often use the camera and the flashlight and the presence of the Arabic language is necessary for me, I'll wait for a more stable and multilingual version.

Thank you anyway for your efforts :good:
[Android General] bigrammy:
Super busy at work so :(

I will have a play around when I come off shift but I am pretty sure this will be fixable ;)
[Android General] HypoTurtle:
I've went back to L_V3 (had to restore individual apps - using backup&restore app - as couldn't restore full userdata.img backup with SPFlash).

I was about to try a rudimentary multi/dual boot - with MIUI - using the userdata partition; but forgot that it's encrypted now... and can't use sdcard partition...
[Android General] jorjolo69:
I'd like test it. I have a backup of your zoppo port ROM. I use it. The only problem is excesive drain of battery. Thx for your work
[Android General] Xabadou:
Port X002

I have not permission for post links.

Sorry!
[Android General] Nsonaso:
Help me on how to port

Please teach me how to port ROM for MT6732 and MT6752
[Android General] jorjolo69:
Send it in a private message.

Thanks
[Android General] bigrammy:
Hi bro just for info,

Well I finally got around to installing 5.0Beta3 and wow I am pretty impressed :good:

I did a little tweaking here and there and it all seems pretty stable :fingers-crossed:

CWM none touch recovery works great providing you don't encrypt data of course :rolleyes:

No ADB is a little annoying but I have done a quick look through the boot.img and It seems the problem is related to init.mt6752.usb.rc and this new Function Filesystem :rolleyes:

on fs
mkdir /dev/usb-ffs 0770 shell shell
mkdir /dev/usb-ffs/adb 0770 shell shell
mount -o uid=2000,gid=2000 -t functionfs adb /dev/usb-ffs/adb
write /sys/class/android_usb/android0/f_ffs/aliases adb

A little more info can be found here https://plus.google.com/111524780435806926688/posts/AaEccFjKNHE but I need more time to dig through it all properly :laugh:

CM12 Kernel

I added the kernel header and used it for the recovery and it booted fine but still no TOUCH :crying:

Lets hope the Blaster gets an upgrade to L as their Kernel's seems to be the best without any doubt. :fingers-crossed:

I won't spend too much time debugging this Beta3 as Beta4 will probably be released soon :fingers-crossed:
[Android General] HypoTurtle:
Look at #3, you can get adb with KingoRoot, it installs its own adb driver that works well, I've lost adb a few times, but just need to run Kingo again to regain it.

V3 is prerooted if I remember correctly?... Hopefully we'll have something from the Just5 guys, I'll try and recompile TWRP in Omni5.0 if I get the chance this week.
[Android General] bigrammy:
I have fixed the 5.0 BetaV3 adb problem boot.img Here ;)
[Android General] bigrammy:
5.0 Beta3

Hi,

Ive been using this 5.0 Beta3 ROM now for a couple of days and is it just me or what :silly:

I cant seem to fault it in anyway :confused:

Only problem was enforced data encryption which I disabled prior to flashing and adb which I fixed after flashing.

Volume up + power gives Recovery - fastboot and normal boot options and boots to recovery without any problem :confused:

Charges no problem power on or off :confused:

I get OK battery life it's fast smooth and the sound seems fine :confused:

CWM recovery works fine backing up data with no problems :good:

I am really confused only thing I can think is maybe any problems are data encryption related as I have never encrypted my data :eek:

I just wondered If anyone else finds it OK :eek:
[Android General] HypoTurtle:
Only issue(s) is GPS - unless that's only me. No problems with running encrypted data.

And the only thing I can see other than that, that people can complain about is that they haven't pushed it to OTA yet. (With a disclaimer regarding GPS).

They haven't released v4 on schedule, perhaps they've realised the move to 5.1 would be relatively seemless and are working on a 5.1 OTA.

[MENTION=3924647]bigrammy[/MENTION] have you managed to compile the kernel? It's cutting out on me and I'm not sure why.
[Android General] bigrammy:
Only thing I have not tested yet is the GPS :laugh:

I have just acquired an HTC ONE M7 and thought the ROM development would be far in advance of our MTK's but how wrong I was :(

There are far more bugs in the custom and official roms than ours all the usual suspects cameras bluetooth sim battery life etc etc :crying:

I think I will be staying with MTK and pocket the cash savings :good:

I have not even attempted to start compiling :o

I am kind new to linux and compiling so it will be a big learning curve for me that will take a lot of time for me to get my head around :laugh:

If [MENTION=5480061]Santhosh M[/MENTION] has not managed it yet I seriously doubt I would stand any chance at all :laugh:

I am kind of hoping that the Just5 Blaster release 5.0 as It seems they have a better or cleaned source drivers etc. :fingers-crossed:
[Android General] Santhosh M:
What kernel or what help is needed ? If it's about the L kernel it uses 64 bit kernel for which the source isn't there and hence i can't compile. I don't think it's kitkat ? :confused:
[Android General] bigrammy:
Hi bro,

Carliv suggested maybe we could try recompile TWRP in CM12 environment to see if we can get it working on L. :eek:

CM11 TWRP with the KK kernel will not boot at all :confused:

CM11 TWRP boots but then crashes with the L kernel so we can't see if TWRP can start the touch.

I still don't really understand why the recovery can't use the KK kernel because in theory it should still work so I can only guess the LK (Uboot) is doing a kernel check and kicking it out. :confused: (Just a theory with no proof :laugh: )
[Android General] HypoTurtle:
It was the KK kernel, I have it compiling now; just had to get it dirreced to the right CC. [Can't test if it boots though as I'm on LP atm.]

Can you list the adb changes? It stall boots for me (likely the encrypted data) - but did give me adb on Ubuntu.
[Android General] bigrammy:
Hi mate,

Modded boot.img log

Enforced encryption is disabled I commented out. #setprop vold.post_fs_data_done 1 and in fstab set data to encryptable.

ADB Fix:

Replaced init.usb.mt6752.rc I can't remember which one I borrowed now :laugh:

Replaced adbd file in the initrd/sbin I think this was the main cause of the problem.
[Android General] HypoTurtle:
Xposed on 64-bit Lollipop

Just to clarify, and to save others time/effort:

xposed is working on Lollipop but isn't working on 64-bit (arm64-v8).
[Android General] HypoTurtle:
New custom ROM ports

Couple new ROMs/Firmwares from [MENTION=5593006]z0rgent[/MENTION]

Also on Updated #54