yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] kentdream:
broke my 987 screen yesterday. kinda sad. order a screen replacement from china and follow the youku video.

Had sucessfully replace the screen, touch operation works fine. ***This screen has very thin glass, rought 0.4mm. ****

if anyone interest to see what happen to the glass, i will post a pic of it.

Be warned:

For who may need to do screen replacement, the RF attenna wire is very fragile.

I've broke one of the plug result no 3G/GSM signal.

replacement wrire is on its way.
[Miscellaneous Android Development] Pe3ball:
That was fast,receiving the replacement from China in one day :p (sorry i just saw you are from Hong kong :) ) Please post a picture of the broken glass to see it.I guess you had no screen protection and case cover?
[Miscellaneous Android Development] ohagas:
Whao, great work, I need to change mine also. Tell me, was it difficult and how long did it take you?

The guy in the video link has a hair dryer...did you use one?

I don't understand why the video is 26mins long, even though he has the phone working after around 10mins. Is it all related to the V987?
[Miscellaneous Android Development] gojo.pl:
Hi All

I've found online some solution for invalid GPS data with endomondo or similar soft.

in build.prop should fix the issue. Reported to work correctly, however I wonder if there are any side-effects.
[Miscellaneous Android Development] patientx:
NO Gsm signal at all :(

This was my first post :

And the response back than :

I was out of the city so I couldn't do all this. But ... After a day I sent this message I came back to my home.

I first tried reflashing recovery .. Still no gsm signal ..

I left the card inside the phone and was looking for solutions for the problem also downloading latest v3rom suddenly there is an sms beep and I looked at my phone .

It started to get signal ??? So I thought everything is OK and didnt want to reinstall v3rom over my setup again. BUT.....

After two weeks... I moved from my home city to my work place in another city -in which I originally bought this phone-

BAMM! no signal again.

This time I flashed latest cwm recovery + V987_extended_userdata_mod2_-_2GB_USRDATA + latest v3r02 rom. Still no signal. Tried a sim from another phone still no signal :(

It actually says : ***cell (my provider) Only for emergency purposes. SO it sees the sim card kinda knows the network but no signal at all.THERE IS A ? IN A SIMCARD ICON next to gsm icon.

This happens in both slots. Please help.
[Miscellaneous Android Development] bgcngm:
Could you please check if IMEI numbers are valid? Go to phone dialer and use code *#06#.
[Miscellaneous Android Development] kentdream:
i had put a case cover and screen protection, but none of these prevent the disaster happened.

screen cost about usd$27 and RF attenna cost USD$1.

Here is the cracked screen.

see how thin is the glass.

small pilers, hot air dryer(is a must), magnifier, tiny philips screw driver, plastic pryer(to seperate the top case and middle case)

between the screen and pilers, there is a black wire. (they said is the RF attenna), replaced a new one , and 3g signals came back.

It took me around 30mins to remove the screen. about an hour to complete.

Don't forgot double-side tape. u need them.

i broke that black wire result no 3G/GSM signal, display an sim card icon with question mark (similar to member patientx said), i read some forum articles in china, 1 of user said he has no signal too, return to zte service point, after inspection, serivce-man said the RF attenna has fall off. it may not be your case.

some info for v987 users, brought a Toshiba Exceria 32Gb(Type HD, UHS-I) microSD card, it works with v987 phone.

The new screen work flawlessly, everything is fine EXCEPT now i have 2 questions about proximity sensor and v3.0r2 rom camera apk.

1. proximity sensor. My sensor is no long functioning. When normal, you place your phone near your ear, screen off. after that, screen on, right? Now is not working. can some one kindly advice what can be wrong? can i check proximity via engineer mode to see if proximity sensor is working/or unpluged? So i don't have to disassemble the phone again? Please?

Is this the proximity sensor in red circle?

2. I take the opportunity upgrade to rom v3r2. I love the old camera app(found in v2.0 rom) user interface, how can i get it back?

Here is another link how your v987 looks inside.

http://www.soomal.com/doc/20100003834.htm

I saw there was a link for service manual directly from zte support, but that link is dead, does anyone has a copy of that so i can take as reference to fix my sensor problem :crying:

The video was so long, to me, sounds like he wasn't well prepared before taking video, and he does spend sometime to introduce viewers to buy parts from his shop.

Replacement process wasn't that difficult as long as u working it out slowly and carefully. removing the broken screen was the hardest part. i didn't brought the black case(which hold the screen) was immediately regret,

coz i don't have spare double side tape, however i manage to use some 3M automobile double side tape(thin one, like 0.2mm)

need to remove broken piece by pieces.
[Miscellaneous Android Development] zperetz:
http://yadi.sk/d/B8YqzJ2Y8_k5z

Here's the copy of service manual. Enjoy!
[Miscellaneous Android Development] zperetz:
Bruno, here's some question we have explored.

Maybe you've heard about the BeatsAudio libraries, it makes the sound on the phone much better. You can find them attached, they should be installed through CWM. But it drops the phones with V3 ROMs to the black screen even without ZTE animation (only recovery helps), while on stock ROM everything goes smooth and nice. Could you please check the problem?
[Miscellaneous Android Development] ohagas:
Thank you so much for posting this kentdream!

When I ordered my replacement glass I bought the LCD assembly also. It cost around $60. Here is the link: http://img.inkfrog.com/click_enlarge1.php?image=V987_LA.jpg&username=wwhhower&aid=174887862

With the assembly does it mean I don't have to separate the glass with the hairdryer?
[Miscellaneous Android Development] kentdream:
thank you so much for your help.

that is just the touch sensor+LCD assembly.

Pic below, on right hand side, is the black top part which hold the LCD.

Unfortunately, you will need hairdryer remove old glass, Heat up the old screen till the screen is barely untouchable.

turn over the black case, pill off the copper sticker, use screw driver help to seperate from black case.

Tweezers to remove broken pieces.

Clean them up so your new screen will place in a perfect level position. (youku video did mention about this).

Use ethanol spray (electronic contact cleaner usually contains ethanol) to clean up old double side tape residual.
[Miscellaneous Android Development] ohagas:
Thanks kentdream. I managed to fit the new glass today.

Everything seems OK except 1 thing...the main camera doesn't seem to be working (the one on the front works OK).

Any ideas what could be wrong?
[Miscellaneous Android Development] angemon10:
Phone (internal) memory problem

SRS WOW HD doesn't work at all in my phone (V2.0 MOD). I tried Android stock music player and no effect at all :(.

New problem

I have problem with internal memory. It's capacity is 980 MB (I didn't extend it nor did try). Appplications use 514 MB and cashed data use 1,59 MB. I have only 163 MB available! There should be free space over 400 MB, and I remember very well I had it several weeks ago. WTF, like I have WP8 phone with "other" storage issue :crying:!
[Miscellaneous Android Development] ohagas:
Actually, I just got it working. I had the Snap camera app installed. I uninstalled and reinstalled and it's great! I'm a happy man. Now to order a flip cover..those screens are thin!
[Miscellaneous Android Development] bigas:
Friend, there's something that always happens with CyanogenMod: log files.

Try the following: with a root browser, navigate to ROOT/data/log. See if there's any log files in there. Usually with my Samsung, a ton of 1MB log files are created and get you out of space quickly.
[Miscellaneous Android Development] patientx:
OK; it seems imei is not valid in my country , so the person I bought it from said to use this command to change imei :

And ;

Also I had use the same imei for both of them and voila! it is working again. I wrote this because someone else might stumble upon this problem too.

BTW, I entrede engineering mode through Gravitybox.
[Miscellaneous Android Development] angemon10:
Thanks

Thank you very much :laugh: :good:.

I found root/data/log_other_mode folder and searched about it. It was full of various log files and they are safe to delete.

216 MB are back!

Can't believe how much it use :eek:.
[Miscellaneous Android Development] bigas:
I'm happy you understood that the instructions would be the same although you're not using CyanogenMod. ;)

Enviado do meu dispositivo móvel.
[Miscellaneous Android Development] fryta22:
Hi friends, did you find how to get rid of this "G" and "3G" letters ? Maybe change this for H like HSDPA or G for E like EDGE ? :p :p Maybe is possible change colour for blue, like clock colour ?
[Miscellaneous Android Development] bgcngm:
You could get rid of G and 3G, but your last sentence makes no sense at all: "G" and "3G" symbols represent the type of network the phone is registered to, not the type of mobile data connection established.

While "3G" means phone is connected to a WCDMA network, "G" means it is connected to a GSM network. On top of that, with respect to mobile data connection, you can either get H+ (HSPA+), H (HSPA), 3G (UMTS), E (EDGE) or G (GPRS) symbols over the network bars. For example, while connected to a GSM network ("G" letter showing) you can only establish EDGE or GPRS data connections.
[Miscellaneous Android Development] fryta22:
Hi, thanks for your quick answer. First sorry for my poor English. Second thanks for great ROM for zte v987.

I know what you mean class speed GSM network.

I would like three options:

1 Completely remove the letter "G" and or "3G"

2 Changing the colors of the icons from green to blue, the color of the watch

3 Change the letters "G" to "E" and "3G" to "H"

Can you tell me how to do it? Where to find these options in the system?
[Miscellaneous Android Development] bgcngm:
You don't seem to have understood what I wrote above, so please read it again.

As for hiding or changing colors of network connection type symbols, that can only be achieved by either modifying the ROM or implementing that functionality on GravityBox, which is the best option as it gives every user the free choice. I will look into that when / if I have time.
[Miscellaneous Android Development] zperetz:
Bruno, will you have time to look at BeatsAudio issue, or you don't think you will?
[Miscellaneous Android Development] bgcngm:
Sorry, I missed your post. So, you say that BeatsAudio libs work when installed over stock ROM, but not over mine? I wonder what the problem could be... but the first thing that comes into my mind is that stock ROM doesn't support init.d scripts and mine does. Could it be those scripts? Are you sure that those libs provide any effect when installed over the stock ROM? I'll have to run some tests.
[Miscellaneous Android Development] zperetz:
I don't know if it can be scripts, I'm not so good in it, but I believe that files from my previous message should explain everything to master like you. I can just confirm that on stock ROM these libs really work and sound becomes much better.

The instruction for stock ROM is:

to install this .zip through CWM and then remove MusicFX.apk and .odex from system/app. Then after reboot everything should be great and crystal rich sound will make your life colorful and lovely forever :)

But in our case instruction is not working, no happy life, crystal sound and other things, just CMW recovery - restore after battery out/in.
[Miscellaneous Android Development] ndouchin:
I found a workaround for my mvno in order to cancel the 'R' of roaming display. By editing framework.jar.
[Miscellaneous Android Development] bgcngm:
Hmmm... do you just hide the R symbol or have found a way to disable it only for your MVNO? Because if you are just hiding it, that can already be done with GravityBox. ;)
[Miscellaneous Android Development] ndouchin:
I really manage to avoid the R , not only disable the display.

all is in the method :

private boolean regCodeIsRoaming(int paramInt)

{

IccRecords localIccRecords = (IccRecords)this.phone.mIccRecords.get();

SIMRecords localSIMRecords = null;

if (localIccRecords != null)

localSIMRecords = (SIMRecords)localIccRecords;

String str1;

if (localSIMRecords != null)

str1 = localSIMRecords.getSIMOperatorNumeric();

else

str1 = null;

String str2 = this.newSS.getOperatorNumeric();

boolean bool1 = false;

if (5 == paramInt)

bool1 = true;

if ((this.mServiceStateExt.ignoreDomesticRoaming() == true) && (bool1 == true) && (str2 != null) && (str1 != null))

{

log("ServingPlmn = " + str2 + "HomePlmn" + str1);

if (str1.substring(0, 3).equals(str2.substring(0, 3)))

{

log("Same MCC,don't set as roaming");

bool1 = false;

}

}

int i;

if (this.phone.getMySimId() == 0)

i = SystemProperties.getInt("gsm.sim.operator.numeric", 0);

else

i = SystemProperties.getInt("gsm.sim.operator.numeric.2", 0);

String str3 = this.newSS.getOperatorNumeric();

Log.d("GSM", "numeric:" + str3 + "mccmnc:" + i);

boolean bool2 = this.mServiceStateExt.isRegCodeRoaming(bool1, i, str3);

if ((bool2 == true) && (str2 != null) && (str1 != null))

log("strServingPlmn = " + str2 + "strHomePlmn" + str1);

for (int j = 0; ; j++)

if (j < this.customEhplmn.length)

{

int k = 0;

int m = 0;

for (int n = 0; n < this.customEhplmn[j].length; n++)

{

if (str2.equals(this.customEhplmn[j][n]))

k = 1;

if (str1.equals(this.customEhplmn[j][n]))

m = 1;

}

if ((k == 1) && (m == 1))

{

bool2 = false;

log("Ignore roaming");

}

}

else

{

return bool2;

}

}

i just change some value in this array :

private String[][] customEhplmn = { { "46000", "46002", "46007" }, { "45400", "45402", "45418" }, { "45403", "45404" }, { "45416", "45419" }, { "45501", "45504" }, { "45503", "45505" }, { "45002", "45008" }, { "52501", "52502" }, { "43602", "43612" }, { "52010", "52099" }, { "26207", "26208" }, { "23430", "23431", "23432" }, { "72402", "72403", "72404" }, { "72406", "72410", "72411", "72423" }, { "72432", "72433", "72434" }, { "31026", "31031", "310160", "310200", "310210", "310220", "310230", "310240", "310250", "310260", "310270", "310660" }, { "310150", "310170", "310380", "310410" } };

by some plmn of my country included my mvno and the real physical plmn

=> Thus in the GsmServiceStateTracker.smali file you have to replace this :

const-string v8, "46000"

aput-object v8, v7, v6

const-string v8, "46002"

aput-object v8, v7, v5

const-string v8, "46007"

by :

const-string v8, "20801"

aput-object v8, v7, v6

const-string v8, "20810"

aput-object v8, v7, v5

const-string v8, "20823"

my mvno is 20823, and my sim is "multi IMSI" , able to connect to sfr or orange
[Miscellaneous Android Development] bgcngm:
Thank you. That is a great finding indeed. ;)
[Miscellaneous Android Development] C3C076:
Nice find.

Btw, in your specific case,

it would be enough to return 1 from com.mediatek.op.telephony.ServiceStateExt->ignoreDomesticRoaming().

(assuming there are no other 208 domestic operators you want to treat as roaming)

This is how default implementation looks like:

.method public ignoreDomesticRoaming()Z
.locals 1

.prologue
.line 116
const/4 v0, 0x0

return v0
.end method

This method is called by regCodeIsRoaming. If it returns true and MCC of operators is equal (208 in your case)

then it's not treated as roaming.
[Miscellaneous Android Development] ndouchin:
[MENTION=455439]bgcngm[/MENTION], thank you, you can talk about this method on the first post , if you want.

[MENTION=5008415]C3C076[/MENTION] my method is indeed not the most effective. And your code is more simple, and correct for all national roaming.

Maybe it could be include in the future version of your custom rom bgcngm.
[Miscellaneous Android Development] C3C076:
Maybe it would be enough to add something simple (and generic - not only for MTK) like CM has:

https://github.com/CyanogenMod/andr...mmit/a3897015d7d41b42b2c7b4a13e055683a93e1d4d

Shouldn't be too much work to implement it in GravityBox.

I checked the isRoamingBetweenOperators method and it's identical since ICS up to android 4.3.

A little more effort has to be done for MTK having Gemini since the check is related to the particular sim slot.
[Miscellaneous Android Development] ndouchin:
isRoamingBetweenOperators is not called by v987. At first i was looking for the problem in this method, as it was implemented. but not called by Zte....
[Miscellaneous Android Development] C3C076:
Yes, I found that out later.

Nevermind, for Gemini devices we can do that using that other method.
[Miscellaneous Android Development] ndouchin:
Do you know how can I change the value of the value "Preferred Networks" .What is the purpose of this setting?

You can edit , but changes are not saved. And with my sim card I have something wrong, it says proximus (20601 - belgium!!???) instead of 20823 or 20810?...

This menu is bewteen "Data Connection" and "Acces point Names" in mobile parameters.
[Miscellaneous Android Development] kakodemon:
Looks like the lockscreen "lock" icon is not centered, any way to fix that?
[Miscellaneous Android Development] lmcteo:
long keypress not working

just got this phone and i noticed that compared to all my android devices, this is the only one which doesn't have any functionality if i hold and press (long keypress) the home button. this is also the case for the menu button. is this normal? if not, i really hope that this is a software issue. is there anyone with a similar experience?

by the way, i'm using stock 4.2.1 ROM and had just rooted it.
[Miscellaneous Android Development] tsiglas:
No this isn't normal....just press and hold the home button between the end of the screen and the and the home button...it should open the latest apps that you have use....trie it several times to find the write place to press.

The menu button is working with no problems anywhere...

Noone has problem with the menu button as far as i know...
[Miscellaneous Android Development] KopiJahe:
Some Questions

[MENTION=455439]bgcngm[/MENTION] I have ZTE N986, the specs are just the same as V987, but it is CDMA-GSM, not GSM-GSM device. I have some questions that might be helping me achieve what you did on V987.

1. How did you able to use AOSP camera?

Firstly, I hate that ZTE use 3GP container even for their 1080p format (3GP conatiner with MP4+AAC in it), I flashed aosp camera from all over the xda, but always failed to enter video mode.

2. How did you edit EBR files?

My N986 have the same partition as your V987, some people succeded to change their partition with MeteOS ROM edit app. but did you manually change it with some app, hex editor maybe?

Thanks in advance
[Miscellaneous Android Development] kentdream:
Glad to hear you had the screen replaced !:good:
[Miscellaneous Android Development] Pe3ball:
Hello.I have recently installed this rom in my ZTE v987.Today when the alarm turned on the phone was stock and it was saying android upgrading start apps.I had to remove the battery to stop the alarm sound and to close it.Also this message appears sometimes when i boot the phone and then starts normally..I installed the rom with default settings and made wipes.I have the latest gravity box installed 2 days ago.Anyone having these issues?

Update. Today I can confirm the same problem with alarm. When it started ringing the phone was stuck in screen android upgrading start apps. Had to remove the battery again to stop it. Please look into this issue.
[Miscellaneous Android Development] kentdream:
Had my broken screen completely replaced. [1] [2] [http://xdaforums.com/showpost.php?p=45272661&postcount=826]

thanks [MENTION=1812476]zperetz[/MENTION] giving service manual :good:

After screen replacement, the FPC/Promixity sensor is no longer working. During voice call, the screen will never turn on until voice call is end.

The only way to trigger the screen on during voice call is to press on the screen hardly right below the noticfication light (@rssaca said twisted the phone also work).

To test your sensor, type *983*0# in dialer , enter test mode. scroll down to "sensor"

If you sensors failed or unpluged, test result will NOT show "ok" or a "numberic value"

The FPC sensor trouble was so inconvinence for me(almost gave up & going to buy a new huawei p6)

so i decide to tear down again and carefuly examine sesnors and found a clue why my FPC sensor is not working.

1. screen is relatively thin, 0.73mm.

2. the black top case which hold the screen has 1mm deep for the glass to fit it (didn't take a pic)

3. double check youku video, that guy has replaced a new black top case and peel off new sticker from it(looks like foam type tape).

4. I've use the wrong thickness(1mm) of double side tape. Besure you get some LESS THAN 0.3mm double side foam tape.

carefully examine the glass, FPC sesnor area only allows certain amount of light to be transmitted.

FPC/Proximity Sensor, if the glass is too far away from the sesnor... the signal will not go throught the glass therefor sensor test will trigger a value of "OK", means blocked, & screen off. While pressing hard on screen below the FPC sensor, the glass get closer to the sensor so the singal can go through the glass. Giving out a value of "1.0" in sensor test.

I've cutted some used sticker and re-attach on the black case, the glass stick a lot closer to the sensor and FPC back to life again.

using a lighter as sensor obstacles.

Nothing block ~

Blocked ~

Pls bear with me, english is not my primary language, hopefully this 2cents tips can help other 987 users.
[Miscellaneous Android Development] kratos69:
Excellent ROM.
[Miscellaneous Android Development] reglaspv:
I have a simple question, probably with a complicate answer but still, I'm looking for a short answer :)

It is possible/relatively easy/easy/hard/impossible to adapt 4.3 or 4.4 to our devices?
[Miscellaneous Android Development] bgcngm:
It is hard / almost impossible to achieve that because MediaTek full sources are not available to public.
[Miscellaneous Android Development] kratos69:
Bruno, first of all thanks for all the work done. The ROM is excellent. I found a bug in Settings - Options development - Limit processor in the background. I put four processes but to restart put back "Standard Limit"

Can you solve this?

Excuse my English, Spanish translated with google.
[Miscellaneous Android Development] reglaspv:
Ok, thanks for answer.

So, it's all about MTK MT6589 and probably the reason why other roms for similar devices in the world (QMobile A900/Life Play/Symphony w150/Gionee elife E3/General Mobile Discovery) works but with some issues on the same hardware.
[Miscellaneous Android Development] zperetz:
Bruno, what about BeatsAudio libs issue. Had you time to check?
[Miscellaneous Android Development] onizukao:
I've done all the steps but can I lift the sub-board at 90 degrees or I risk to break something?

I've lift it only some degrees but in this way I could not put the double-sided tape...

Thank you!
[Miscellaneous Android Development] reglaspv:
I assume that you remove the black antenna cable and the left PFC cable.

In that case, it shouldn't be a problem to lift the board, because there are no other screws or locks, just another flexible data cable on the upper side of the board.
[Miscellaneous Android Development] onizukao:
No, i've removed both PFC and antenna cable.

I just want to know if I can raise the sub-board at 90 degrees without breaking the flexible data cable on the upper side, I did'nt try because I was afraid to break something...
[Miscellaneous Android Development] bgcngm:
I did and I've run into the same problem, stops booting with libs installed. Have no idea what could be the problem. Let me do further tests.