yashsingh1/xdaforums huggingface dataset:
[Android General] GoJo ^^:
Ok well thanks, i just installed the one you gave me and i'm restoring a backup (i was trying 4.4.4 meanwhile); i do not see "mount USB storage" however, your screenshot has it.. Why?! Vibration every button press is annoying, why they didn't put an option to disable it :( Are there other non touch recovery for 5.0 roms?

PS: Seems there aren't any customs for 4.4, only 5.0? Looks like i'm going to stick to Lenovo rom for now if correct; how can i disable the home button backlight once and for all? For now, after each reboot it's back, turned on all the time.. ><
[Android General] HypoTurtle:
I think I've got them all here; except AmigoUI.

Mount USB storage should be there - this is external sdcard not the virtual internal (/data/media); maybe that is why it doesn't appear. TWRP has mtp mount - which mounts both. Latest compile attached. You'll need to use adb:

adb shell
twrp

to see the options.

Capacitive buttons should turn the button backlight off. Not sure if anything can be done about the vibration - I don't mind it.

If you're not committed to a ROM yet - give the AmigoUI a try, could use some feedback on if it works properly for someone else.
[Android General] bigrammy:
[YOUTUBE][/YOUTUBE]

Sorry they don't meet with your approval Sir we will all try harder :(

If Sir would care to look at the top of the page there is something called a search box maybe you should try it sometime. :rolleyes:

Some people :laugh: :laugh:
[Android General] GoJo ^^:
First link send be back to my post, mistake I guess..? Second, the twrp file, can't I just rename it to IMG and flash with rashr? Where'd you get the last twrp file?

Lastly, my backup made with the other recovery (cache bug) couldn't restore with the one you gave; have to be careful about that.. Thanks for all!
[Android General] HypoTurtle:
Fixed the link (it's to #54); the twrp is a zip you just need to unzip to get the .img and that can be used with rashr/fastboot etc - no need to rename; I compiled that myself, mainly due to carliv making a P6000 device tree for recovery.

WIth your backup - what recovery was used to make it, typically you would need the same recovery (or at least recovery type CWM/TWRP etc.) to restore it. I think you've backed up in a CWM (perhaps carliv CWM) and are restoring with cofface CWM? If so then there must be too much difference between the two in terms of backup/restore. There are obvious ways around it...
[Android General] GoJo ^^:
Post is #292 here, maybe cause im on the mobile app.. Anyways, whats the best 4.4 rom to you?

Vibe with GravityBox gives great results so far.. About that new TWRP still needs to have data & system backed up at once?
[Android General] HypoTurtle:
4.4.4 - probably Flyme for me.

TWRP - as there is no touch - it's just over adb as I said but no you can choose what to backup.

adb shell

twrp backup SDC

etc.

info - here

The link is fixed in the original post (will still be broken in your quote).
[Android General] GoJo ^^:
Oh I see.. no touch, forgot that! What's better in 4.4 ROM compared to 5.0 exactly? Currently I'm trying to fix the extsd write permission.. Without success :(

PS: Shouldn't be able to access quick settings while screen's locked, how do I change that? And how to TOTALLY disable the LED? Couldn't find a way..
[Android General] GoJo ^^:
I made a backup with the cofface recovery yesterday, today i needed restore, it did it quickly but then i'm into a bootloop..!!

Wiping cache didn't help, was forced to do wipe data :( Is there a known bug? I guess you'd have told me..?

Another thing: advanced restore doesn't seem to work at all.. So far i gotta go back to zero it seems..?
[Android General] HypoTurtle:
Without logs (adb logcat) it's hard to see what the problem was... there are system/ROM specific files located in /data so perhaps some conflict happened... advanced restore works perfectly fine for me with cwm/twrp - haven't used cofface as much but it's just another version of cwm.
[Android General] GoJo ^^:
Well the other, less appealing, cwm do backup/restore normally.. I made 2 backups with the cofface cwn, all restore without issue but then bootloop..?! Maybe backup to internal sd is corrupted but not to external? There's an issue anyway and not just for me.. ;)
[Android General] bigrammy:
I have modified the fstab file in this version of cofface recovery Lollipop only.

Hopefully this will fix the backup/restore issues :fingers-crossed:

I cannot test it because I do not have the P6000 with me just now.

https://copy.com/2iVlPBtqVcwizjWy
[Android General] GoJo ^^:
Thanks, i'll report if i have enough time (and balls :D) to test it. New question : how do i make my LP rom display more than 4 notifications icons in its bar?! It sounds crazy but that's how it is, after there +4, a 3white dots icon will show, telling you there are more notification hiding. But there is space for +15 in the bar..!! I looked everywhere : rom settings, gravitybox, google.. Couldn't find anything :/

EDIT: Oops! Looks like another sh** did pop-up..! When i used the other "recoveryL" recovery (sorry i dunno its name), the one that worked, i did backup on ext sdcard. An hour i did backup with it on internal memory. Now i was looking in ES Explorer where it sent that backup and.. I can't find it!! Wait.. I found it! It's in mnt/shell/emulated/clockworkmod. What the hell?! Looks like there's indeed an issue with backing up to int sd..
[Android General] bigrammy:
No Idea. :laugh:

CWM Recovery's are not ideal for Android 5.x due to vold but as there is no touch function in the Kernel then we are stuck with it....

Vold decides where to put the backup on the internal_SD as it is vold managed. :rolleyes:

Make your backup's to MicroSD instead. :good:

I only changed some of the blocks to the actual dev block number rather than the link type as mount only returns those below.

So boot, nvram, lk (uboot) and logo are by block number eg:

boot -> /dev/block/mmcblk0p7

just incase there are any mount issues. :eek:

output of mount

/dev/block/platform/mtk-msdc.0/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered)
/dev/block/platform/mtk-msdc.0/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/dev/block/platform/mtk-msdc.0/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/platform/mtk-msdc.0/by-name/protect1 on /protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/platform/mtk-msdc.0/by-name/protect2 on /protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/platform/mtk-msdc.0/by-name/custom on /custom type ext4 (ro,seclabel,relatime,data=ordered)
[Android General] HypoTurtle:
This sort of thing would be due to how the ROM boots stuff and also multiuser support etc.

Recovery will have either /data/media or /data/media/0 mounted as /sdcard

and /mnt/media_rw/sdcard1 as /storage/sdcard1 in CWM or /external_sd in TWRP.

You should find the clockworkmod folder and backups at these locations in all ROMs, the other places are symlinks/vold-mounts from these, in Vibe for example what /sdcard points to I believe even changes if you are in root shell # as opposed to normal $.

Not sure what would cause a bootloop other than not enough /data space for dalvik-cache to rebuild or incorrectly formatted /cache. A logcat would definitely point out the issue here though.
[Android General] GoJo ^^:
No sorry, i got plenty of free space! And bad news : i tried the new recovery, same issue : after backup/restore from internal memory, i get a bootloop.. Oh wait, actually it's not really a "bootloop" : the phone just reboot and goes back to recovery, that's it. The Vibe rom is great (after fixing wifi), only issue i have is the notification bar showing only 4 icons..

PS: How to FULLY disable home button LED so it stop blinking when you're using the phone and get notification..?
[Android General] mtllo:
hi,HypoTurtle,

I try to transplant amigo 3.5 out in three days
[Android General] HypoTurtle:
AmigoUI 3.5.23 from http://www.needrom.com/download/gionee-elife-s7/ works fine, or at least as well as the previous. There is an update to 3.5.24 available. There is still an error regarding nvram (wifi error) - I suppose my nvram might be corrupted - but just need to bypass the SetupWIzard to get into the ROM.

V3.5.24 is available here
[Android General] HypoTurtle:
Amigo UI - v3.5.24 (OTA updatable-ish)

Install procedure:

Install this custom recovery.

Download the latest official ROM.

Download this zip.

Reboot into recovery

Install the official ROM.

Install the additional zip (P6k-5.0_files-AMIGOUI.zip)​

OTA updates

When any update is available (ignore the ones that report broken system) these should install correctly but you should reinstall the P6k-5.0_files-AMIGOUI.zip

This procedure should continue working, but I can't guarantee​

Bugs

Not sure if battery charges correctly when screen is on (could be a power drain somewhere)

Front camera with stock camera will FC

There's likely more, let me know.​

Hints/Tips

MTK Engineer Mode is *#GIONEE# (*#446633#)​

Credits

Gionee for the ROM

And credit to mystory for the inital needed files.​

Notice

I will try and keep this as upto date as possible. The ROM is just en/cn and there are some chinese apps preinstalled - as Gionee's markets for the S7 are just China and India. I may post a zip to strip the chinese apps, but for now the ROM seems to be usable.​
[Android General] brabagul:
Sir hypoturtle

Hi again sir, i just want to ask if what chipset did you port it from? i tried porting ROMs from 6752 to my be pro 6732 but still camera and home button still doesnt work.

i ported 6732 flyme os got the camera and home button working. i applied the procedure to fix it in flyme os 6752 bugs (camera, home button) but still the bug is still there.

im wondering if the chipset affects the camera and home button or its just some files i need to replace

hoping for your reply
[Android General] HypoTurtle:
Most of the ROMs seem to be from MT6752; Flyme is from M1 Note, the 5.0 ports; VibeUI and the AmigoUI posted above are both from 6752, so not sure what would be the difference between the two Ports. The only issues are relatively minor - a QuickSetting that doesn't work or the front camera in the stock app.

Are you trying with wiped /data or a dirty flash? There could be something there that's interfering - a logcat might find the camera problem, not sure about the home button.
[Android General] brabagul:
Hmm.... I'm wondering why i really can't fix the camera and Home Button, p6000 and Be pro are same 6732 and has same mount points i think.

you've told me before that porting threads could help me out but it seems i still couldn't fix it. maybe because all of those are old porting methods.. If you have some time some extra time, i could really use a help here.

when i flashed my ROMS i wipe all mount point, data, cache, system.

ill try using logcat, maybe it's some camera permission. not so sure
[Android General] vikmaffia:
Are you connecting on 5GHz? I've seen reports of poor wifi signal and throughput using 5GHz. You could try connecting on 2.4GHz.
[Android General] mtllo:
amigo ui , I will send here

http://xdaforums.com/general/xda-assist/p6000-amigo-3-0-lollipop-t3134068/post61320431#poststop
[Android General] Gausa:
No I am connecting with 2.4 GHz channel 11.
[Android General] GoJo ^^:
Using vibe rom, had WiFi issue and used a fixing app, thought it was gone but no.. WiFi had to be disabled/renabled after some time; despite icon looking fine, data doesn't go through.. Any fix for that? And a way to fully disable led n notifications while screen's on..
[Android General] xenonism:
WiFi works very well here on Vibe, so I can't help you. To gain complete control of the notification LED, I think you need GravityBox.
[Android General] GoJo ^^:
Fact is I have it, looked EVERYWHERE into it and also other led control apps.. Can you tell me how to proceed?
[Android General] xenonism:
I'm still in the process of installing Xposed, but I found something on the Elephone forum. As soon as I find the exact page again, I will update this post.

Ok, so Total Notification Control is a premium feature, so you have to either donate (any amount, apparently) via Paypal or buy the unlocker on the store to enable it.
[Android General] GoJo ^^:
I do have it, but i couldn't understand it I gues.. Did you?
[Android General] HypoTurtle:
Gravity Box => Display Tweaks => Button Backlight mode => Disable button backlight

Simple enough...
[Android General] GoJo ^^:
Ahah.. Yeah but that is for when you press it, doesn't change anything for notifications..
[Android General] xenonism:
Are you talking about notifications or just the button being on while using the phone? For notifications check my post, for the other issue check HypoTurtle's.
[Android General] GoJo ^^:
Man, I did read and reply your post.. But anyways, I may have found a way, but it's bit great. Normally, notification light shouldn't turn on while you're using the device. But turning it off totally isn't great either.. Still less annoying though..
[Android General] xenonism:
I didn't mean to be rude, it was just getting a bit hard to figure out what you actually wanted. :) Personally, I like the light to be on while using the phone, I wish the other two hardware buttons were also illuminated... Matter of taste, I guess.
[Android General] GoJo ^^:
Yeah.. I was wrong anyway, didn't found a way to get rid of it. Are you happy that it flashes while watching a movie..? Guess not. There should be a way to temporarily disable it at least.. Can't find tough!

But I found a way for notification icons limit issue! Just put data monitoring in "auto" mode, it'll be in center of the bar, which will allow extend notification icon limit.
[Android General] xenonism:
Well, no, I meant I like the light to be on while I am interacting with the phone, as in touching it. I don't remember seeing the light flash during playback, though.
[Android General] mtllo:
[amigo 3.5.24] , Is ready, but it is not perfect, at present there are two bugs I haven't found can repair him, don't use dat format packaging, with the traditional zip format, easy to modify, after here is my download.

http://xdaforums.com/general/xda-assist/p6000-amigo-3-0-lollipop-t3134068/post61371822#post61371822
[Android General] @cidflash:
Hello, I have a quick question for the best . with any rom I have no access to the rear camera . Only the front camera works but with the upside down .... Can you help me ?
[Android General] GoJo ^^:
Sounds like hardware issue...
[Android General] JakVot:
The same here...
[Android General] HypoTurtle:
P6000 or Just5 Blaster
[Android General] @cidflash:
Yet when I received it worked great ! I just changed for Rom
[Android General] HypoTurtle:
Same behaviour the stock ROMs (4.4.4/5.x)??
[Android General] GoJo ^^:
Quote from you on the elephone forum; I guess 644 is read only? My brightness file is already set this way but the notification light is still here.. how to disable it for good?
[Android General] anchal joshi:
Things work out

I hope this will work out and it make the operating of this system better
[Android General] JakVot:
Stock:

4.4.4 Not tested

5.0 20150417 Camera Not OK

5.0 20150611 Camera OK

Vibe 2.5 20150601 Camera Not OK

CM12.1 20150525 Camera Not OK

Seems that my P6000 HW/Camera (bought in May) is different and supported only in the newest stock...

/sys/hwm_info/hw_module_info from 20150611:

[ Main Camera ]:

chip :

s5k4h5yc

mipiraw

vendor:

id : 0x485b

[ Sub Camera ]:

chip : gc2355mipiraw

vendor:

id : 0x2355

/sys/hwm_info/hw_module_info from 20150417:

[ Main Camera ]:

chip : gc2355mipiraw

vendor:

id : 0x2355
[Android General] HypoTurtle:
Either have a script manager run that at boot or use Capacitive Buttons apk - which will do that for you.

It seems that way - a Samsung sensor instead of a Sony. It should be just the kernel you need, Vibe should work after switching the kernels, not sure about CM12.1.

Where did you get it from? Do you know the manufacture date (sticker under battery)?
[Android General] JakVot:
Thanks I will try to change the kernel. I got it from coolicool, ordered in middle of May. There is no exact date under the battery cover. I will check the paper box once at home.
[Android General] HypoTurtle:
Date on battery might a good indicator anyway - might has a small rectangle sticker with the 12 months and a mark on what I take to be the date of manufacture.

For unpack/repack boot.img

Once you have it unpacked can you post the new kernel... might as well start using that in ports.
[Android General] GoJo ^^:
Nope, capacitive buttons disable the backlight being turned on all the time. It doesn't disable notifications flashing, which is what I'm talking about (as you know.. I hope?!);

I finally found a way : with the app light manager, to alternative mode & sleep mode. Seems I finally killed that *****.
[Android General] XdaTotoNIni:
Hello,

I have the same problem of camera upside down for front camera, and back camera not working in vibe ui.

Phone received 3 days ago from EverBuying.
[Android General] giaki3003:
[/strike] Elephone P6000 source released [/strike]
[Android General] HypoTurtle:
Try this boot.img with VibeUI
[Android General] XdaTotoNIni:
It worked thanks :)
[Android General] rionline:
[/strike] Elephone P6000 source released [/strike]

damn, not the 5.0 source, hm?

where do you get this info from, giaki3003?
[Android General] giaki3003:
Dang just realized now...

I intended p7000...:eek:
[Android General] GoJo ^^:
Anybody tried the last VIBE rom?
[Android General] bayad:
Yes, I tried it and everything is working great for me :D
[Android General] GoJo ^^:
Wi-Fi is really fixed?
[Android General] schizo99:
Not charging while powered on.

Hi,

All of a sudden my phone is not taking charge while powered on.

It is charging fine if I power it off!

Do you have any ideas?

Note: I have not made ANY changes to the phone when it stopped taking charge.
[Android General] greekfragma:
Most possible scenario is that your charger is not giving enough power. Try a computer usb cable to charge it. If it charges with usb the charger is faulty.
[Android General] vikmaffia:
Same for me, with any other charger too, including a 2A one.

Also, the phone does not sleep and depletes the battery in ~12 hours According to Better Battery Stats it's because of USB Suspend kernel wakelock - the phone thinks it's connected to a pc (?). I suspect that the USB port is faulty...

Can you check your wakelocks with BBS?
[Android General] schizo99:
I have no issue about battery drain, I'm currently in shanghai so not possible to download BBS for me.

After a suggestion I used high pressure air to cleanout the micro-usb port and after that it works.

But it feels so strange that it worked while the phone was off.
[Android General] GoJo ^^:
Why can't download in shanghai? You can find the apk on many website..

PS: Can only get 2G on SIM2.. Heard people could get 4G, so why not even 3G here?
[Android General] bayad:
Yes, Wifi is working great also :)
[Android General] n7of9:
I'm looking for a device to use as a wifi hotspot and I'm seriously considering the P6000. I am not interested in using it for phone calls at all.

I have never used a dual-sim handset before, how does that work? Can I use the P6000 with a data-only sim?
[Android General] GoJo ^^:
Why not..?!
[Android General] mite_jan:
hi

i have just received the elephone p6000 and it came with Lollipop

the thing that i dont like is when i try to scroll very slowly at the beggining it jumps couple of pixels but then it is fine

i am aware that there are some fixes on the internet for the scrolling but are those fixes really going to help solve this problem ?

also looks like i have the model with samsung camera chip inside

is this better camera than sony ?

can i try stock kitkat with working camera ?
[Android General] HypoTurtle:
Sounds like the screen scroll issue from the first round of devices, the fixes on #2 should work to fix it, but not sure if the fixes work on 5.0 ROMs.

Not 100% but if you want to try a 4.4.4 ROM, switch the kernel with the ROM you're on now - it should work but haven't heard from anyone that's tried it.
[Android General] mite_jan:
probably later i will experiment with the touchscreen fixes

touch is functional now but i hate those little jumps at the begining with the slow scrolling

i have lollipop now

you mean use the lollipop kernel inside 4.4 rom ?

i dont think it is going to work this way
[Android General] HypoTurtle:
The kernel should be compiled with 32bit compatibility. That's why it might work with the 4.4.4 ROMs - I just haven't tried it. Just the kernel, not the whole boot.img
[Android General] Elephone1:
Can you record a video of your situation, so I can know more what happens with your phone. :p
[Android General] schizo99:
I thought I replied to my question but perhaps I didn't.

In any case, after suggestion from a friend I used high pressure air and cleaned out the micro-usb port and now it works.

Still very strange that I was able to charge while it was turned off.
[Android General] mtllo:
Based on Lenovo K3NOTE transplant, Lenovo original firmware only English and Chinese, I extracted from the CM12.1 language, now it supports 80 languages

VIBE 2.8 Lollipop Download :

https://drive.google.com/file/d/0B7w-gT-bd5zoWHB5ZFR6a0lxU1E/view?usp=sharing
[Android General] mite_jan:
give more information

any bugs ?

how good it is compared with the existing vibeui 2.5 rom on elephone forum

btw isnt vibe 2.8 based on android 5.1 ?
[Android General] mtllo:
android 5.0 1526
[Android General] GoJo ^^:
mtllo, please post screenshots! ;)
[Android General] mtllo:
vibe 2.8 screenshots

Our machines have no 3.10.65 kernel android 5.1, transplant lenovo K3note android 5.1, at the same time, lenovo official released two 1526 version of the VIBE, an android 5.0, an android 5.1, although the VIBE version of android 5.0 is 2.5, it did, in fact, he and VIBE2.8, so I change it to version 2.8.

This ROM is no problem,And we don't support the kernel gestures, gestures function cannot be used in the ROM. I only found the drop-down status bar flashlight does not work, but I make up a flashlight APK, other normal use!

Due to the ROM itself only in Chinese and English language, language pack from CM12.1 extracted in this ROM, a total of 80 languages, but part of the translation is not very complete.

Android 5.1 VIBE 2.8 can boot but many bugs, no signal induction, no photo no sound no distance estimation is caused by our kernel is 3.10.61. If our machine has 3.10.65 android 5.1 kernel estimate these bugs.

Lenovo K3note original firmware

http://phonedl.ota.lenovomm.com/dls/v6/VIBEUI_V2.5_1526_7.234.1_DEV_K50-T5_WC0B.zip

P6000 vibe 2.8 download :

https://drive.google.com/file/d/0B7w-gT-bd5zoWHB5ZFR6a0lxU1E/view
[Android General] mtllo:
Hi,HypoTurtle.

FlymeOS source code is open, we can carry out patch!

https://github.com/flymeos
[Android General] HypoTurtle:
Nice, so they've gone open with 5.0 then...

Have you checked the kernel version used in the CM12.1 ROMS?
[Android General] andrei80:
Hello and thank you for the effort of porting these roms!

I am very happy with stock 4.4.4 right now. Is there any reason to switch to Vibe 2.8(I am not asking about other LP roms because they all seem more or less buggy)? I am asking about stability, bugs, pros and cons. Thank you!