yashsingh1/xdaforums huggingface dataset:
[Android General] greekfragma:
My knowledge on compiling is not much but I remember older phones to implement new hardware features once they got a new firmware by unlocking those hidden things by software means, so my guess is that we can make the OTG work the way it should.

Also about the compass, manufacturers in general avoid to design different hardware versions to keep the cost down. So they just hardware-lock something and disable it from even appearing as a locked feature.

The examples are lot. I will just remind you of the computer graphics card technology that even 10-15 years ago you got a GPU with locked pipelines which could unlock just with flashing the bios from the stronger version of the gpu.

My point is, that the newly presented 64-bit Mediatek SoC just got out and as always, before it becomes mainstream, the 1st version can be the hidden treasure as history teaches. Only one way to find out ;)
[Android General] xenonism:
Yes, I'm well aware of the practice of artificially crippling hardware, but I'm not an expert in the mobile/SoC field, so I thought I'd ask around. We'll see! :)
[Android General] greekfragma:
Few moments ago I found a new OTA update for my phone from Elephone.

20150131

approximately 23mb of files downloaded.

Started the download but right after the unzipping of the package and before the restart was done to start update, I got Warning error

Nothing seems broken. Only thing not working now is OTA feature disabled. :eek:
[Android General] Poppeye0:
You did remove the little plastic strip that covers the battery pins to protect from discharging? No offense, just making sure.
[Android General] enr88:
What Fw you had before download ota update?
[Android General] vikmaffia:
There was no plastic strip whatsoever, maybe that was the cause of the problem. BTW the battery is at 0,85V and won't accept the charge. Dead.
[Android General] greekfragma:
My device was shipped with 20141228.

After update I still have the same.
[Android General] HypoTurtle:
My phone just arrived this morning - I've got the same version atm. 20141228 (build date 20141227-164154) - can anyone give me a way to see the jumpy touch... I've tried show pointer location in developer settings but I can't see anything worth complaining about; just to see if there's a difference before and after the update.
[Android General] xenonism:
Someone said this game is a nightmare to play without the fix: https://play.google.com/store/apps/details?id=com.miniclip.eightballpool&hl=en
[Android General] greekfragma:
try to scroll up-down left-right on menus really slow. If you have the lag problem you will see small jumps.

My build is 8.3_20141228-011521

Maybe on your build you already have the correct screen driver :)
[Android General] HypoTurtle:
Thanks I'll try a screenrecord before and after.

I think I just saw the jumps - only with very slow scrolling. My screen driver is 1-ili9881_hd720_dsi_vdo (from MTK Droid Root & Tools v2.5.3), and gt9XX_config seems to have the 0x00'ed real values. If it makes a difference mine came from gearbest (took 4 weeks from purchase to delivery)

Edit. Also found PCBA Mode and you can see the jumps while testing in there. Anyone have any idea as to if PCBA is META mode or something else??

According to tracking mine took 2 weeks to get to the UK, and was sat there for two weeks (customs??). I'lll test the fix after a full backup.
[Android General] greekfragma:
Mine arrived from Gearbest also in 17days time. I am sure after you get the fix you will see the difference more clearly. :)
[Android General] xenonism:
In an Italian forum some people were complaining that the notification LED acts erratically after installing the 20150109 ROM. Any evidence of that? What about the update released today via OTA?
[Android General] greekfragma:
Another guy here in Greece with 20150109 rom also send me a pm that his notification led is not pulsing when charging. Today update was ok for some people and failed for others. I failed to update on mine but I do not know if the blame is on my rom build or because I installed the screen fix before this one.
[Android General] the1024:
yes, with this update led works like on that fw released for spft.

guys says that it is the same firmware, just pushed for ota.

i doubt that touchscreen fix breaking update. as my tpd fixed and i reflashed to 20141228 and successfully updated with ota
[Android General] greekfragma:
I am sorry but i did not understand what you are writing about the led. After this update the notification LED works as it should or no more pulsing when charging?
[Android General] the1024:
oh, sorry. yeah, it's not pulsing, with usb connection it always lit up
[Android General] enr88:
Like on 01/09/15 Fw

Before OTA, you flash with spflashtool the fw 12/27/14 that we can find on needroom?
[Android General] the1024:
yes, like on that firmware.

no, i flashed from my backup. think it's the same as needrom firmware, haven't checked
[Android General] HypoTurtle:
The OTA (EU-WEST) can be found here

[MENTION=3164405]the1024[/MENTION] [MENTION=4205141]enr88[/MENTION] ;installed fine for me from 12282014. From the looks of it it's hust patches and an updated uboot.

[MENTION=4945676]vikmaffia[/MENTION] I can see a difference between the dots on slow/fast swipe before applying fix.

screenrecord might be a bit better than screenshots: #screenrecord /sdcard/screen.mp4

Edit. Yea the change in dots is noticable; needed to apply the fix a few times though.

Has anyone played around with the settings (USB) - in engineering mode??
[Android General] enr88:
Hi guys, even with this update zip i have the same recovery error http://xdaforums.com/showthread.php?p=58634547

I'm on 01/09/2015 Fw.
[Android General] the1024:
[MENTION=4205141]enr88[/MENTION]

you can't install i on this firmware. it is intended for 20141228 and has binary patches that cannot be applied to other version.

new update has new build date, but basically it looks identical to 20150109, so i assume that elephone slowpokes just pushed update to ota with delay
[Android General] vikmaffia:
I enabled 'show pointer location' and got these results. The dots would be evenly distributed and few millimeters apart, regardless of the speed of the swipe. Once you perform the patch, the dots are much much closer if you swipe slowly (even almost touching), but will be more apart in case of a quicker swipe.
[Android General] xenonism:
Hmm... Do you think it's a good thing or should they always be close?
[Android General] vikmaffia:
I think it's not disturbing, the sample rate per second is probably the same (I guess). The important thing is that when you do precision moves, it follows accurately.

I can send you some screenshots if you want.
[Android General] the1024:
[MENTION=3356343]xenonism[/MENTION]

this is normal touchscreen behavior. when you move quicker - jumps are greater.

problem with ours was that minimum jump length was set to 30 px for some reason
[Android General] xenonism:
Sure, I just wanted confirmation that no new problem was introduced. Thanks.
[Android General] troyanryller:
In my case OTA fond update 20150131, successfully unzip then reboot and update. But after turn on in OTA i see old 20141228 version(second time update did the same). I got touchscreen fix by method 2, tried to reflash by this, but after reflash touchscreen fix still worked and OTA to 20150131 gives no result again.

@the1024 can you give your 20141228 backup?
[Android General] the1024:
of course. here
[Android General] HypoTurtle:
Long press home => Recents seems to be broken with the update (or my fiddling). No biggie tho.

Screenrecord attached showing the much improved jump length after the fix.
[Android General] kestrelv2:
Nonsense, you are the only p6000 user without the touch issue remember. How can it fix what isnt there.
[Android General] greekfragma:
Get a life kid and stop messing with me. Do something useful instead of flaming other members.

I had the phone on my hands for 3days and the use was not that much to see the lag problem on the screen. I am also used to scroll fast and the lag was obvious only on slow touches. Also I do not play games so I did not test it there.

I have reported you again. I hope there is a perma thread ban for you because I had enough of your attitude.
[Android General] kestrelv2:
Flaming is what you just did, not me im just quoting what you wrote.
[Android General] bigrammy:
Emergency Number FIX for dialing 123 UK 3 Voda Spain etc etc

I fixed the problem for those who have 123 as customer services voice mail etc which on this phone call the Emergency Services :eek:

Dialing the long number did not work for me as I still got Emergency Services Again!!!

This is a serious problem as we can be prosecuted in the UK.

I saw there was no support from elephone yet again.

Anyway I found an easy fix now.

Root required: Go to root file manager and navigate to system/etc/ecc_list.xml select the file in Text EDIT mode and Remove the line <EccEntry Ecc="123" Category="?" Condition=? /> save and back out. Reboot your phone and boom no more calling of Emergency Services.

123 are alot of users service providers contact number eg: voice mail, customer support etc etc.

This will work with any other number in the list you have problems with :good:

Hit Thanks. :cool:
[Android General] HypoTurtle:
It was actually patched with yesterdays update.
[Android General] thecuki:
annoying mmi test

hi,

is there a way to disable mmi test thats popping up all the time on p6000, even after completion?

also, how to adjust screen gamma, my old thl w200 got nicer colors :).

if you are to choose between those 2 models and coolpad F1 8297W (2gb 16gb 1920x1080 13mp Octa Core) as third, which is the best in your oppinion?

thanx in advance
[Android General] HypoTurtle:
Settings => Display => MiraVision => Menu ???

Haven't seen mmi test.
[Android General] thecuki:
thanx

somehow i missed popup menu in miravision first time.

the test is called lxt mmitest
[Android General] vikmaffia:
CPU downclock

Do you guys know of any CPU tuner app that can handle our MTK soc properly? Preferably switch off cores, or at least limit the max frequency.
[Android General] bigrammy:
Typical I spent hours on that :rolleyes: :laugh:

Still my phone's firmware (k01q_e:4.4.4/KTU84P/1419698357:user/test-keys) never got the update so it still may be helpful for those who never got a fix. :eek:

Is the 123 reference gone altogether now I just wondered what they did to fix it is it by way of reference or simple removal of the 123 context. :confused:
[Android General] xenonism:
Does anyone have a clue what apk/patch/setting in the latest update might have broken the "home button breathing while charging" feature? Thanks!
[Android General] HypoTurtle:
They just removed it:

<?xml version="1.0" encoding="utf-8"?>
<EccTable>
<!--
The attribute definition for tag EccEntry:
- Ecc: the emergnecy number
- Category: the service category
- Condition: there are following values:
- 0: ecc only when no sim
- 1: ecc always
- 2: MMI will show ecc but send to nw as normal call
-->
<EccEntry Ecc="112" Category="0" Condition="1" />
<EccEntry Ecc="911" Category="0" Condition="1" />
<EccEntry Ecc="000" Category="0" Condition="0" />
<EccEntry Ecc="08" Category="0" Condition="0" />
<EccEntry Ecc="110" Category="0" Condition="0" />
<EccEntry Ecc="118" Category="0" Condition="0" />
<EccEntry Ecc="119" Category="0" Condition="0" />
<EccEntry Ecc="999" Category="0" Condition="0" />
</EccTable>

It would likely be something in framework
[Android General] bigrammy:
Cool I did it sort of right then :laugh:

Lets just hope I don't have a disaster in a country where 123 is the proper number :eek:

You think this would be a simple location thing and that numbers would be enabled or disable according to which country you're in still this works for now. :rolleyes:
[Android General] xenonism:
Thanks. I certainly have a lot to learn. :o Any other known regressions in the update?
[Android General] gleam2003:
Yesterday no update for my P6000 that was already v8.4

Today find an update via official system. Update to v8.4 (but it's already 8.4?).

Download via updater software 48MB, i find the update that user save from yesterday and was only 24MB. Why? Different phone?

My phone dosen't have touch issue at all and lag on scroll, i don't apply any patch...

...i don't save the zip and now i can't find it on the phone sorry.

Sorry for my bad english.

Today 6/02 elephone remove from here forum discussion about touch and realese an apk for update the TP firmware, i don't use it because my touch work fine for what i do with it.

Add the apk from elephone forum in attached

Also add the bin and cfg file extracted from the apk
[Android General] Nukomod:
Does the Russian fix also work if I update to the 31 Jan build first? Elephone also posted a screen fix on their site, but it's less accurate than than the Russian fix (still 4 px off in stead of 1).
[Android General] greekfragma:
I want to ask for something the xda members participating here. Is it possible that someone can upload the latest Rom. My OTA update is broken and I can't update my phone now. I have already done the russian fix but not sure if it is 4px or 1px steps. Sometimes it goes from 1pixel right to next one (on straight lines) but sometimes jumps 3pixels away (on circle movements).

And one last question. If someone that has the latest ROM has the notification LED working as it should (pulsing when charging device and blinking when message comes)
[Android General] enr88:
You should flash stock ROM 28/12/14 with spflashtool then update via OTA. No problemi with this procedure, before i cant get OTA..

Unfortunately led not work as it should..
[Android General] greekfragma:
Let me rephrase because maybe you did not understand me clearly.

My phone works good. Notification Led works as it should. Screen fix is ok. And everything on the phone is ok. But, if Elephone releases a new update that fixes more things I can not update through internet OTA app.

Now only thing that doesn't work is the storage mount on PC. So I can't transfer files to or from SD card.

Should I stay as I am for now, or reflash the smartphone, patch the fix with 1px (i do not want 4px fix) and fix my OTA update?

I do not want to lose the Led notification features that are working as they should. People that flashed with OTA said LED is not working anymore.

Pfff....so confused
[Android General] xenonism:
I went back to the old ROM because I also don't want to lose the notification function; on the other hand I don't know what I am missing from the update... Does anyone know? At least one person reported being able to use encryption after the update.

I can't mount the phone as mass storage either, but I can access my SD card in MTP mode on both Linux and Windows systems, so it's more of a matter of principle than an actual issue. If only we could fix that notification thing... Unfortunately I don't really know where to start.
[Android General] HypoTurtle:
Download Light Manager to fix/improve the notification function - I tried to find what broke it in the OTA but was unsuccessful - then I remember it was a notification light and found the above app.

[MENTION=622119]greekfragma[/MENTION] I'll try and catch the OTA download address if/when there is one like I did with the previous one.
[Android General] Xpresso38:
Hello.

Thanks to all of you, who make ours P6000 working better :o

My phone working great, i'm very happy about it ! (screen smoothy , and got new recovery :D )

I try to help someone on french forum who as bootloop, after a mistake to install recovery.

I don't find anyway to help him.

Do you have any solution ?

A way to flash with spflastool ?

This is my first post here, sorry for my poor english.

see you soon.
[Android General] HypoTurtle:
Just read the last couple of pages from the thread on frandroid - I think you're looking for this thread => SPFlash P6000
[Android General] Xpresso38:
Hello HypoTurtle.

Thank you for answer.

I'm reading, and i understand you'r all making incredible work to made a recovery with touch.

I got another noob question.

I've made an nandroid backup with cmw_carliv.

Got an file nandroid.md5

How can i use it if i need to flash this rom, with spflashtool, must generate a scarterfile from this?

And when P6000 is powered off, is it possible to start directly in recovery?

I actually use Mobiluncle Tools to reboot in recovery.
[Android General] taylerdurden:
Can you post wich camera sensor do you have in your P6000, and the purchase date? It seems that there are 2 versions of Elephone P6000 camera, one with Omnivision 8858 sensor, and one with Sony IMX219 sensor.

You can see it in /sys/hwm_info/hw_module_info
[Android General] Xpresso38:
Hello.

Mine have imx219mipiraw , i ve bought it on geekbuying, 31/12/2014.
[Android General] xenonism:
Same here, bought from GearBest at the beginning of January. I'd say it's the Sony sensor.
[Android General] enr88:
Sony imx219

Aliexpress 01/07/2015
[Android General] xenonism:
Thanks for the app suggestion. I'd still prefer not to depend on an app for functions that can work natively, another matter of principle I guess.

I am slightly baffled by the lack of information, both from Elephone and especially from the community, about the update. All I know is the notificaton regression and that encryption was fixed.
[Android General] HypoTurtle:
.md5 is just a text file that contains a number that is the md5sum of nandroid.zip (just a file check done by recovery to make sure the nandroid.zip isn't corrupted).

With spflashtools you just need to use one of the ROMS on needrom.com and unzip. Inside there is SPFlash Tools along with a scatterfile and all the .img's needed to restore, the nandroid backup can only be used (as is) within recovery.

From powered off => power + volume up will enter recovery.

IMX219; Gearbest; 05/01 (before second preorder round).

Yea it's likely there was patch they had for the light, that they missed when they updated source for the OTA, typically the notification lights is controlled by lights.default.so (system/lib/hw) but that wasn't touched by the update.

If you look through the update.zip it's hard to tell what's been changed with the OTA as it is a proper OTA using patch files, personally it's just minor bug fixes, fixed encryption I'd say is due to the updated uboot. It would take some tedious reverse engineering to determine the exact changes.
[Android General] PaulTT:
And both sensors have only 8mpx...so we only have 13mpx interpolated. Another difference between the actual product and the listed features...

L.E. - mine has the Sony IMX219 - first preorder round.
[Android General] xenonism:
Yep, I did take a look at the update but it's like you said it's all binary patches with no notes...
[Android General] HypoTurtle:
That's the OTA from 12282014. ~23MB

The OTA from the stock ROM - 01092015 ~ 48MB is here EU-West

Both take the version number to V8.4_20150131, but with the 48MB update long hold home => recents still works, the update from V8.3 broke it, just thinking out loud be perhaps the 23MB update was meant to be an update to V8.4_20150109 rather than to V8.4_20150131.
[Android General] greekfragma:
Hey man. Thanks for the links.

Can you please advice what to do on my situation described here?
[Android General] xenonism:
Interesting... But when I try to update from V8.3_20141228 with the 48MB zip, I get a fingerprint build mismatch. Is it supposed to work? It is safe to force the update? Any info about the notification issue with the 48MB update?
[Android General] HypoTurtle:
the 48MB is meant to take the stock ROM to V8.4_20150131 so won't run from V8.3, you could try and force it (install update.zip in recovery) but I wouldn't imagine it doing too much with V8.3 - at least nothing positive.

Notification light doesn't 'breathe' with the 48MB update - the only thing I've noticed is the long press => recents is fixed; an issue that no one else has reported. Edit I think i's just my issue; as I switched to phablet mode.

Currently trying to restore my encrypted data partition following the SPFlash - without to much joy atm.

[MENTION=622119]greekfragma[/MENTION] - not sure what you're issue is...

If it's just installing the OTA, then just take the update.zip from the OTA zip and install that in recovery, notification light issue is still there though. The OTA only works correctly (without the need to extract update.zip) with stock recovery anyway.
[Android General] xenonism:
Thanks for the info. :) I did try to force the update in recovery, it wouldn't work. I meant disabling/altering the fingerprint checks, or at least trying to.

Anyway, I won't bother updating until the notification issue is somehow solved - I find V8.3 quite usable, anyway.
[Android General] jag123123:
No touch fix in my P6000

I followed the instructions but in my P6000 nothing happens. Something wrong? The drivers are properly installed and ADB detects the terminal but none of the two methods seem to work. Can anyone help? Thank You
[XDA Assist] Aldrin Manabat:
Can someone please help me to install cwm(or any kind of recovery) in my device O+ 8.16

These are the specifications:

O+ 8.16 Quadcore Features/Specifications

Network: Quad band GSM/Dual Band WCDMA

Display Type: TouchScreen

Screen Size: 5.7-inch 1280×720 pixel resolution IPS Display, Dragontrail Glass

Sim: Dual SIM/Dual Standby

WiFi: WiFi, WiFi hotspot

Bluetooth: YES

GPS: A-GPS

Internal Memory: 8GB internal storage,

RAM: 1GB RAM

Card Slot: expandable via microSD up to 32gb

Camera: 13-megapixel autofocus main camera with flash

Front Camera: 2-megapixel front facing camera

OS: Android 4.2.1 Jelly Bean

Processor: 1.2 GHz MTK6589 quad-core processor

GPU: PowerVR SGX 544MP GPU

Air Shuffle Music, Photos, Camera and FM radio

Flip to Silent, Shake to Answer/Hang-UpCall

Battery: 2500mAh Battery
[LG Optimus L9 P760, P765, P768, P769] QA Bot:
Q&A for [ROM][4.3.1][P760][unoff.] CyanogenMod 10.2 [STABLE] [OC/UV] [05/12]

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

Before posting, please use the forum search and read through the discussion thread for [ROM][4.3.1][P760][unoff.] CyanogenMod 10.2 [STABLE] [OC/UV] [05/12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[XDA Assist] praneeth91:
i rooted my htc one m8 and flashed with TWRP rom and installed lollipop and it worked fine till i restarted my phone and now it switches on directly goes into my boot menu and selects hboot and says

sd checking.......

no gift file.....

loading.....

no image!

loading....

no image or wrong image!

loading...

and askes me to press power button to reboot and again the same thing happens as a loop. i just have no idea what to do can anyone help:(
[XDA Assist] Darth:
Hi,

Did you update your firmware recently with a file from your SD card? If so... The file needs to be deleted off the card. But either way, take the card out and see if you can boot ... If you have one in.

For further help, you can ask in this help thread in your device section,

http://xdaforums.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783

Good luck!
[General SlimRoms Discussion] TESTCN:
BING translator

install Slim-i9100-4.4.2.build.5-OFFICIAL-4068，all is good ，no Problem。About 10 days after，phone connected to the computer USB， can't see Some files ，For example movie file Folder，These files are present。

Screen LOCK Occasional fail。

Standby，not use phone，the phone Very hot。

phone connected to the computer USB to copy file，Speed is very slow 0kb/s----4mb/s

MTP connected to the computer USB to copy file,can't copy，phone system Disconnect usb
[JASJAR, XDA Exec, MDA Pro General] BYJO:
I have an apple mac, how can i sync my Xda Exec to my computer as it only runs on windows.I really want to listen to music and save the files on my xda to my mac. Can someone please help me?