yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] bgcngm:
Ohhh... okay, that issue I have as well. But seems to be better now with the new kernel.
[Miscellaneous Android Development] EMF:
Have the same problem. Try to long press on the top half of the home button, that seems to work, and others have confirmed the same.
[Miscellaneous Android Development] DaKyy:
Yes that seems to work for me aswell.
[Miscellaneous Android Development] Wolfillete:
Hi! I can't connect to 3G/2G with V2.0. APN seems well configured but it doesn't work with Vodafone-ES. Actually is not phone's problem because it works with other companies... Any solution?
[Miscellaneous Android Development] demstav:
Same here
[Miscellaneous Android Development] Wolfillete:
Solved, just phoned my operator

I have another problem, with rom v1 I cant set a network-based location (not gps) for weather app, etc. It seems the option is turned on but is not working. Maybe could it be problem of my network provide again??
[Miscellaneous Android Development] bgcngm:
Arghhhh... ZTE did major changes to the lockscreen. I haven't yet managed (and don't know if ever will) to revert to the AOSP lockscreen. However, I have found out that a custom ROM shared over Chinese forums is using Holo Locker to simulate it.
[Miscellaneous Android Development] zperetz:
For me, and for lots of other users, the main issue with ZTE stock lockscreen is volume buttons, which are not actually blocked. You can live with "touch & hold", ok, used to it, but it's hardly possible not to push volume buttons in your pocket. Is there any solution for it?
[Miscellaneous Android Development] reglaspv:
I have on my V987 the exact unlocker you mentioned and is a pain if i use my phone with my left hand.

If i try to unlock, as my thumb goes to the right side of the screen, the base of my finger touches the camera icon and instead unlocking the phone, i open the camera app.

If I try to answer, in the same way, before my finger touches the right circle for answer, the base of the finger touches reject call circle and inadvertently close the call instead.

Using another unlocking app, I can change just the way the phone is unlocked and not the answering part, which means I still got a lot of people angry with me for rejecting their calls.
[Miscellaneous Android Development] bgcngm:
I don't know if you have been following development of GravityBox, but more and more features are being added to it. Some had been included on my previous custom ROM releases and taking into consideration that GravityBox now implements those, I will integrate the module in the next release.
[Miscellaneous Android Development] zperetz:
I've heard about it, of course, but never installed. Just had no chance. Will try now.

Update: very cool, a lot of customization. But it does not solve the issues with volume buttons on the lock screen.

By the way, to get the list of last applications you need to touch & hold the roof of the home button. There's a difference where to touch :)
[Miscellaneous Android Development] reglaspv:
Hi Bruno,

I've just flashed V2Mod and Titanium fix but I can't restore my apps because Titanium is stuck at the beginning of the restore process.

There is something more that I can do? There was no error in CWM, when i flashed your rom or Titanium fix.

I solved Titanium problem. I used custom install in Aroma and didn't check Titanium for install, because it was already included in my backup.

Then, I restored/installed it as user application, rather than system application and the fix was ineffective in that particular situation. I made Titanium a system app and now is working ok.

Please, could you tell me if it is by your design that my 8gb ext-sdcard now is seen as internal sdcard and the rest of internal sdcard (1.92gb) is now ext-sdcard?

Thank you!
[Miscellaneous Android Development] zperetz:
Bruno, can you check this http://yadi.sk/d/JxMXWFu77-Ra6? It looks like we have official update from today.

Update: false alarm. The same B02. ZTE just updated the site, not the firmware.
[Miscellaneous Android Development] Wolfillete:
UP
[Miscellaneous Android Development] instantwater:
Are there any REALLY WORKING solution for "return button problem"?

I'm googleing for 2 days, installed about 5 different ROM version (STOCK, BM, etc...), but neither of them solved that bug, and that's very annoying...

Thanks in advance.
[Miscellaneous Android Development] gerstavros:
Is there any link with full firmware partitions to flash with sp flash tool? Bruno do you know anything?
[Miscellaneous Android Development] instantwater:
"return button problem" workaround

Here's a workaround for "return button problem"

You'll need ROOT access, and a ROOT file manager.

Add the following line to '/system/build.prop':

qemu.hw.mainkeys=0

This will enable on screen keys.

To disable capacitive back button edit '/system/usr/keylayout/Generic.kl'

Find the following line

key 158 BACK WAKE_DROPPED

replace to this (place a # to the beginning of the line)

# key 158 BACK WAKE_DROPPED

To disable MENU button do the same as above but key code is:

key 139 MENU WAKE_DROPPED

For HOME key, the line to look for is the following

key 172 HOME

So you are now disabled all of the 3 capacitive keys, but the button backlight is still turn on in some event.

I haven't managed to turn them off permanently...:(

Tested on Android 4.2 [Bruno Martins V2.0 (07-06-2013)]
[Miscellaneous Android Development] EMF:
I don't have any return button problem after the march firmware update, but had it before. So that solved it for me anyway.
[Miscellaneous Android Development] ulvergr:
I must says that also never had problem with the return button....
[Miscellaneous Android Development] instantwater:
Ah, you're my hero.

Please give me a link for THAT ROM you have installed to solve this.

Thank you very very very very much.

I don't want to send it back to China because of a bug that can be solved in a software way.
[Miscellaneous Android Development] EMF:
It is this one: http://v987.blogspot.dk/2013/03/a-good-custom-rom-for-zte-v987.html

GAPPS from here: http://v987.blogspot.dk/2013/03/google-apps-for-zte-v987.html

But the ROM's by bruno in this thread, should also fix the problem. The version 1.0 is based on the same, and version 2.0 on a newer version.
[Miscellaneous Android Development] bgcngm:
That's totally correct!
[Miscellaneous Android Development] instantwater:
Well I have tried that ROM linked in that blog, but nothing changed about the problem...

Bruno V2.0 is on my phone and it hasn't solved the problem...

Could you send be a CWM backup of your installed and patched and working rom?
[Miscellaneous Android Development] EMF:
No I cannot. It is setup to all kinds of email and other accounts. So no you cannot get a copy of that. Anyway it will not make any difference if you already have flashed the ROM...

Sorry to say, but if it is not fixed by any of the two ROM's in this thread, I don't think you can fix it with software. The march update did seem to fix the bug for all having the problem (including me). So it seems that there might be a hardware problem with your phone.
[Miscellaneous Android Development] gerstavros:
Any help?
[Miscellaneous Android Development] bgcngm:
Sorry, I missed your post. As far as I know there's no such thing. ZTE has only released ROMs in update.zip format. May I ask why do you want that?
[Miscellaneous Android Development] instantwater:
Okay, I'll contact the seller.

Thanks.

---------- Post added at 09:48 PM ---------- Previous post was at 09:15 PM ----------

Here are some new info from the Hungarian forum.

So, this recovery is on my phone currently: "Cwm-based recovery 6.0.3.0 (Compiled by Bruno Martins)"

A guy said to me on the Hungarian forum, I should install "6.0.3.0.7z" version CWM.

Or should I try to install the BM-V?.0 ROM with FLASHTOOL? Because I'm trying to install them by CWM, 6.0.3.0 plain, not the 6.0.3.0.7z

Thanks
[Miscellaneous Android Development] gerstavros:
.7z is the extension of the file, a compressed package, like .zip, .rar :silly:
[Miscellaneous Android Development] instantwater:
Yes it is :) I know, but.... isn't it in the version number?

Okay, I'll restart the tutorial in this topic...
[Miscellaneous Android Development] gerstavros:
it's the same cwm recovery
[Miscellaneous Android Development] bgcngm:
I've just uploaded a new CWM recovery, built from the latest sources. ;)
[Miscellaneous Android Development] instantwater:
Interesting...

I've installed CWM 6.0.3.0 from here, the beginning of the topic, and, then flashed BM B2.0, and my return button is a bit better, but still not perfect.

What should I do to make it perfect?
[Miscellaneous Android Development] alexw801:
To donate Bruno for a beer, as I already advised you on the Hungarian forum.
[Miscellaneous Android Development] instantwater:
Okay I will do of course, after some day testing!

Thanks for the help for everybody.
[Miscellaneous Android Development] ulvergr:
Bruno the recovery can be update only through sp flash tool?
[Miscellaneous Android Development] bgcngm:
The network-based location works based on the availability of cell tower and WiFi access points. Make sure you have Internet connection available for that to work. I can just say it must work because it was tested when I had that ROM installed.

You should, but as alternative you can also use MTK Tools to do that. ;)
[Miscellaneous Android Development] ulvergr:
You should, but as alternative you can also use MTK Tools to do that. ;)[/QUOTE]

if u use mobileuncle toolbox i must flash the rom again?does affect the userdata extended partition?
[Miscellaneous Android Development] bgcngm:
No, using MTK Tools to flash recovery won't mess with any other partition. It's safe to proceed, otherwise I wouldn't recommend it as an alternative. :D
[Miscellaneous Android Development] ulvergr:
thank u for ur quick answer,i have installed MTKtools but how i install the new recovery?
[Miscellaneous Android Development] bgcngm:
There's an entry in the tool where you can choose a recovery to flash (select recovery.img from sdcard).
[Miscellaneous Android Development] ulvergr:
Can u check it?

For updating the recovery only 1 entry i found and doesn't give u the right to choose ur own recovery to flash
[Miscellaneous Android Development] zperetz:
Just checked. You need to put your recovery.img to root directory on your SD card. And then Mobile Uncle will immediately find it in Recovery update.
[Miscellaneous Android Development] bgcngm:
Really strange... the last time I used that tool there was an option to choose a recovery image stored on the sdcard.

Anyway, here's another alternative:

Copy recovery.img to the root of sdcard

Open a command prompt window and type:

adb shell
dd if=/sdcard/recovery.img of=/dev/recovery

EDIT: Okay, seems that MTK Tools still works. ;)
[Miscellaneous Android Development] ulvergr:
There is no option to choose the location of the file u want but as the friend said if u put it at the root of ur sd card the MTK tool find it.

Installed and everything ok. Thank u
[Miscellaneous Android Development] netvpn7:
Hi

any plans to release new version please? I am having problem when on 2g, 3g data works fine.
[Miscellaneous Android Development] gerstavros:
Please, can someone make a read back with sp flash tool and upload it (obviously without his usrdata partition)?
[Miscellaneous Android Development] demstav:
I am having problems with the back button as well. Any plans for a new version firmware?
[Miscellaneous Android Development] bgcngm:
Which partition do you need... and why? I'm curious. :p

I am working on it, but don't have any estimated release date.
[Miscellaneous Android Development] gerstavros:
bruno, a friend with the phone..formatted it using sp flash tool:silly:
[Miscellaneous Android Development] bgcngm:
Hmmm... that's not good. :rolleyes: I'll try to make a backup using MTK Droid Root & Tools, but let me warn you that the last time I tried to load the scatter from a full backup (just for testing, didn't really want to flash), SP Flash Tool warned about a corrupted preloader. Without a good preloader, I don't think the phone can be unbricked.
[Miscellaneous Android Development] zperetz:
And please do not forget about private data :) if we're talking about full backup, which should be done right before the phone is loaded for the first time.
[Miscellaneous Android Development] gerstavros:
Yes i know, i had other times the same problem with read back from sp flash tool, with preloader and dsp_bl, but before sending back i want to try
[Miscellaneous Android Development] instantwater:
I have new interesting experience about the return button issue.

It's more likely to sense random touches on the return button, when I'm in strong sunshine.

In strong sunshine it's going to totally crazy, while I'm in the office, it's working almost without any issue.

Interesting, very very interesting.
[Miscellaneous Android Development] onizukao:
Mmm interesting...

I'm trying to work on the back screws, now i tightened the screws hard...

Inviato dal mio ZTE V987 con Tapatalk 2
[Miscellaneous Android Development] instantwater:
onizukao do you have the same issue?

Is your trying helped?

---------- Post added at 10:57 AM ---------- Previous post was at 10:13 AM ----------

It's maybe not the sunshine, but heat instead?

When I arrived to the office, and put it from my pocket to the table, it still pressed the back button randomly, but now, the phone temperature decreased, it seems to be everything is ok.
[Miscellaneous Android Development] onizukao:
No, it doesn't work. Now i'm trying to loosening the screws but i'ts random, it's hard to replicate it.

I saw a video (maybe on the Russian forum), where the key was activated with the push of a wooden pencil (capacitive key should not)

That's why I thought at the screws.

I think it can be fixed by changing the sensitivity of the keys via software (I hope), Bruno help us! :fingers-crossed:

Edit: I've a screnn protector, do you have one?
[Miscellaneous Android Development] instantwater:
Well, I think so.

It's can be adjusted in the firmware as I imagine.

Whether is it just an integer value, or something more complex?

If it's just an integer, let's fix it and recompile the ROM :)
[Miscellaneous Android Development] onizukao:
A doubt... I've a screen protector, do you have one?
[Miscellaneous Android Development] instantwater:
Yes, but I don't have other protector, so I can't remove that.

Have you tried without protector?
[Miscellaneous Android Development] onizukao:
No, I haven't tried for the same reason :)

But I will try, i'ts the only problem in this phone!
[Miscellaneous Android Development] instantwater:
Yes, it's a fantastic phone, except this bug.

But, if it turns out, without protector works perceftly, how can I protect my screen?

If you have this problem, how can you use your phone?

Have you done my workaround tutorial, or how can you live with this? :D

---------- Post added at 12:57 PM ---------- Previous post was at 12:30 PM ----------

It seems to be reboot helps a bit for a while :laugh:

But I had to do my workaround, because it started going crazy again...
[Miscellaneous Android Development] onizukao:
It's very rare so I use the phone without your workaround.

I'll try to remove the protector as soon as possible.
[Miscellaneous Android Development] instantwater:
Have you repartitioned?

Someboy adviced me on the hungarian forum, try to repartitionate, that may help :D
[Miscellaneous Android Development] bgcngm:
That's crazy... :cyclops: What does eMMC repartitioning has to do with the so called "return key" problem?
[Miscellaneous Android Development] instantwater:
I don't know :D

But who repartitioned, he doesn't have this problem after :D (repartition+install BM V???.0 rom)
[Miscellaneous Android Development] alexw801:
When I purchased the Nillkin back protector case, I received an excellent Nillkin screen protector, I use it, very good!

It was not me who advised you to re-partition.
[Miscellaneous Android Development] instantwater:
Not you :)

That was dwiki. :D

---------- Post added at 02:43 PM ---------- Previous post was at 02:28 PM ----------

May that cause problem, I have installed stock rom with CWM instead of flashtool, and then installed BM V2.0 with CWM,

---------- Post added at 02:53 PM ---------- Previous post was at 02:43 PM ----------

Have you tried BM V2.0 ???
[Miscellaneous Android Development] onizukao:
Yes, it's the same.

Don't ask me why but with a piece of adesive aluminium tape over back button, it is perfect!

http://www.tinyuploads.com/images/IwYBT4.jpg

It is running without problem of "random back button" for 10 hours!

Ok, it's ugly but seem to work...
[Miscellaneous Android Development] ulvergr:
are u sure that is not hardware problem?i have read and others which had the same problem with u but me i had never any problem...

i am thinking that maybe was the the first pieces factory came out and had problems?....
[Miscellaneous Android Development] instantwater:
First pieces???

Mine was produced in 2013.05. There's phones from 2013.03...
[Miscellaneous Android Development] ulvergr:
Just a thought my friend... It is strange, something People have problem and Other not
[Miscellaneous Android Development] instantwater:
Some people have, some not.

Strange.

I've uploaded a video about this bug.

Version information is at the end of the video.

http://youtu.be/LhSCZzHQ_yo
[Miscellaneous Android Development] cappa72:
CWM repartition script

Hi Bruno,

Using your ebr1 and ebr2 files, I prepared a CWM script, which - theoretically - flash these two files without SP Flashtool. This script makes the /data to 2.7GB.

If you can confirm that it works, may the repartition be easier.

Others, please do not use it until Bruno's confirmation.

Cheers.
[Miscellaneous Android Development] onizukao:
If you don't want to use SPFLASH, you can use "Meteos MTK6589 ROM EDIT" to repartition the data partition (i haven't tested it but it should work on any mtk6589)
[Miscellaneous Android Development] cappa72:
The apk you mentioned works I'm sure, but the created ebr1 and ebr2 files will be differed from Bruno's ones.

For this reason it is questionable if the Aromainstaller script recognise the repartitioned /data size.

It is only an assumption, so we need to clarify these things.
[Miscellaneous Android Development] onizukao:
Ok, tested and it works.

I've installed BM Rom 2 and only after the meteos repartitioner. All OK!
[Miscellaneous Android Development] instantwater:
My phone is going back to china..... :(
[Miscellaneous Android Development] kobire:
hi,

when you release the rom with hebrew?

thanks.
[Miscellaneous Android Development] bgcngm:
No release date yet, maybe next week. I haven't forgot about your request, don't worry.
[Miscellaneous Android Development] instantwater:
Will that solve all return button problem?

But I've sent it back to china already .... but I will buy a new V987, because I fallen in love into it :D
[Miscellaneous Android Development] bgcngm:
The "return button issue" has been solved by ZTE a long ago. If you were having that problem it means your phone was probably defective. Me and many other users can confirm that the issue was real back then, but not anymore with the latest releases. In fact, my first custom ROM for V987 is based on ZTE-CN-9B18D-P188F04V1.0.1 B01, which was the first ROM that has the problem fixed.
[Miscellaneous Android Development] netra:
Bruno deserves even a cold beer is hot outside. Let's get a beer in his account.
[Miscellaneous Android Development] gojo.pl:
I'd like to comment on suggested Holo Launcher. I've installed it and visually it looks just ok, but looks like "away status" (screen disabled) is not transferred to the apps. All my friends could see me "online" (not "away") on google talk, like I was using my phone 24h.
[Miscellaneous Android Development] netvpn7:
Hi

How to fix GPS? No luck with fix apps
[Miscellaneous Android Development] wilcovh:
Read about 8 pages back in this thread. there is an explanation how to get gps fix
[Miscellaneous Android Development] rafailo:
I have the same problem any solution?

i tested all the roms , and followed the instructions exactly as described from bruno
[Miscellaneous Android Development] gojo.pl:
Just tried the newest GravityBox 1.8.0 and looks like it disables volume button when device sleeps. Works fine for me.
[Miscellaneous Android Development] zperetz:
Thanks, man. It solves the problem.
[Miscellaneous Android Development] gerstavros:
Has anyone tested 64GB microsd cards if work fine?
[Miscellaneous Android Development] wilcovh:
there have been positive reports, read post 81 and further
[Miscellaneous Android Development] Wolfillete:
Any news from ZTE about android 4.3?
[Miscellaneous Android Development] bgcngm:
I don't think that is going to happen. Probably only on the next MediaTek platform.
[Miscellaneous Android Development] Wolfillete:
:( Well maybe it would be possible to make a non-official port...I hope...
[Miscellaneous Android Development] stvgr:
Originally Posted by demstav

Yes i have this problem with the call not hanging up. Needs reboot after.

+1

new problem:

Another problem is that once you go to make installation of the nova launcher prime makes restart. Please tell me what to do;
[Miscellaneous Android Development] tugof:
I have new problem:

Wifi not working

Bluetooth not working

USB cable not recognized - impossible charging with running system (with system off is OK)

Impossible flashing - flash tool get message: BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)

Doesn´t matter which version of rom. (stock or Bruno)

Any advice??
[Miscellaneous Android Development] bgcngm:
Okay, as a last resort I have decided to port framework from another MT6589 based device and got AOSP lockscreen. There may be another additional features as well, but I still have to run some deeper tests to know if everything is working properly. Is there anyone willing to do some beta tests?
[Miscellaneous Android Development] gojo.pl:
I can try that... hopefully this is stable beta :)
[Miscellaneous Android Development] Sathelp:
Count me in too Bruno if you still need someone
[Miscellaneous Android Development] karamba:
Bruno,

Is it possible to add Hebrew to the next rom version?

Thanks!!
[Miscellaneous Android Development] bgcngm:
Sure, Hebrew support will be added as I already wrote before.
[Miscellaneous Android Development] zperetz:
Put me on the list of beta testers, please :)

By the way, Bruno, we still will work with 2 types of memories, or you had chance to solve the issue with extended memory on full size? Reformating can be a bit complicated for people updating from v1.0.
[Miscellaneous Android Development] bgcngm:
I did it... without porting the framework! :victory: After all, that could lead to all sort of problems and I've decided to abandon the idea. Tried one more time and just made it work, AOSP lockscreen is back. Wonderful!
[Miscellaneous Android Development] gojo.pl:
Great news, then awaiting new release :)
[Miscellaneous Android Development] bgcngm:
I totally understand, but I won't work on that for the moment. The recommendation is obviously to re-apply the modification before upgrading from Android 4.1 to Android 4.2 based custom ROMs.

My idea was to release some kind of CWM installer that could avoid the need to use SP Flash Tool to flash MBR and EBR partitions.
[Miscellaneous Android Development] Wolfillete:
Hi Bruno! I just want to say that you're making an awesome work, I would like to know the half you know about cooking roms for mtk. :)

That's why I want to know if it would be possible to make a cyanogen mod port that could work in every mtk 6589/77 with their respective implementation. That would be the push we need to make our mtk's bigger!