Database Info

BLUBOO D1 - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- F9E62.LTXI.HB.H.SSXS5MA.0623.V3.05: https://drive.google.com/file/d/0BwnyLckVrygrMm1rLXVSQjZHcnM/view
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
- TWRP 3.1.0 by @hsagent : https://mega.nz/#!NAVlSKiI!ySZSJEmo32_okp5k0fA2miG0dhoRfTL8m7_QOmwOYjI​
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

Thank you very much for the stock rom and the recovery but I had a problem... I flashed the recovery but the phone didn't boot. So I flashed the stock rom hoping it would return as new but the phone is still bricked. It only vibrates like it's booting but nothing else happens. It can't also enter in the recovery mode for some reason. Any ideas on what can I do? Thank you for the support

Il_Musce said:
Thank you very much for the stock rom and the recovery but I had a problem... I flashed the recovery but the phone didn't boot. So I flashed the stock rom hoping it would return as new but the phone is still bricked. It only vibrates like it's booting but nothing else happens. It can't also enter in the recovery mode for some reason. Any ideas on what can I do? Thank you for the support
Click to expand...
Click to collapse
Low Battery. (this is what my device does when the battery is empty, vibrates but doesn't turn on)

Charger
Be careful with the charger, mine blew up the very first time I used it, 10 min after unboxing.

Thank you very much, I've successfully installed TWRP to my new device and rooted it.
I have one "issue" with phone, it's not related to root and TWRP, but hopefully you can help me. I'm running latest stock ROM (V3.06). I'm used to run Profile Scheduler for switching WiFi On/Off, changing Ringtone to Vibrate mode etc. This app is able to change profiles based on cell towers ID's. But on Bluboo D1 it doesn't work correctly. I can create profile, define cell towers ID's and run it, it switches profile when ran first time, but after some time it's notification icon disappears and app is not changing profiles then. Based on my observation it's happening after several minutes of non-using phone. I think it's caused by Doze which is killing background service of app. I tried to exclude this app from Doze in Settings/Battery, but no luck. Then I tried app called Disable Doze, it displayed that Doze is disabled after I used it's toggle for Doze disabling, but again no luck and Profile scheduler was killed after few minutes
Do you have any idea how to disable Doze on this device permanently? Or do you have suggestion to any other Profile scheduling app which si working on this Phone?
Many thanks in advance

littlebat said:
Be careful with the charger, mine blew up the very first time I used it, 10 min after unboxing.
Click to expand...
Click to collapse
Hi, i have the same problem

Clight75 said:
Thank you very much, I've successfully installed TWRP to my new device and rooted it.
I have one "issue" with phone, it's not related to root and TWRP, but hopefully you can help me. I'm running latest stock ROM (V3.06). I'm used to run Profile Scheduler for switching WiFi On/Off, changing Ringtone to Vibrate mode etc. This app is able to change profiles based on cell towers ID's. But on Bluboo D1 it doesn't work correctly. I can create profile, define cell towers ID's and run it, it switches profile when ran first time, but after some time it's notification icon disappears and app is not changing profiles then. Based on my observation it's happening after several minutes of non-using phone. I think it's caused by Doze which is killing background service of app. I tried to exclude this app from Doze in Settings/Battery, but no luck. Then I tried app called Disable Doze, it displayed that Doze is disabled after I used it's toggle for Doze disabling, but again no luck and Profile scheduler was killed after few minutes
Do you have any idea how to disable Doze on this device permanently? Or do you have suggestion to any other Profile scheduling app which si working on this Phone?
Many thanks in advance
Click to expand...
Click to collapse
Settings-Inteligent Assist-PureBackground
Turn this off for normal background behaviour.... or select by app.
No idea why this is enabled by default.... Developers!, Bah.

dontmailme said:
Settings-Inteligent Assist-PureBackground
Turn this off for normal background behaviour.... or select by app.
No idea why this is enabled by default.... Developers!, Bah.
Click to expand...
Click to collapse
Thank you, I've tried it but without success unfortunately, Profile Scheduler is still not working properly. I'll search for another profile scheduling app...

Zornicka said:
Hi, i have the same problem
Click to expand...
Click to collapse
Since the charger blew up my phone takes 10-11 hours to be fully charged, and the battery drains up unpredictably every now and then. I installed CPU-Z but there was no info on the current draw, so it's very likely that the charge controller is dead already. Did you get the same behavior?

Thanks to all users who reported the charger issue. I have forwarded all reports to the company and they said me the engineering department is looking into it.
Hopefully the new stock of devices will not be shipped with the same charger.

Live wallpaper not found!
Hello, i have a problem with my device, i have latest android upgrade 7.0 version 3.08, live wallpaper missing, i downloaded soo many live wall app but nothing happens,please do something i need assistance, please help me

Can someone link the camera apk? I've uninstalled it by mistake..

Installed TWRP, rooted, rebooted after wiping dalvik/cache and I can't open any apps :/ Ideas?

Hi, thanks very much for the thread and stock rom.
Do you know if any device/kernel tree sources? Thanks

Twrp builder has released twrp 3.2.3 for this device, which also means we now have a partial device tree for twrp

@Alberto96 I am also looking for device/kernel/blob trees for this device so I can (try) to build Lineage for it. Any ideas? Would the manufacturer help out here please?
Is this device similar enough to MAYA to use the device/kernel trees from that as starting point. The camera is very different.
Cheers 8)

Android Nougat ROMs List for the BLU Life One X 2016

This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.

Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.

elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.

BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.

elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.

review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.

BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.

Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?

tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.

elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?

tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.

elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?

tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.

elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?

tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).

Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.

Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.

tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.

Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]

tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.

[ROM] [Experimental] [LineageOS 15.1] [8.1] [Build 2018-07-05] [Oppo R7f]

First off, huge thanks to all the LineageOS developers. Specially MikeNG for his continuous work on OPPO devices.
Lineage 15.1 is finally here!
Device(s) Supported:
R7f *ONLY*
Don't flash this rom to any other R7 variant
What's working:
* Boot (Much better than not booting obviously)
* RIL (Calls,Text,Data)
* WiFi
* Bluetooth
* Camera
* Audio
* Sensors
* Flashlight
* Notification LED
What's not working:
* Double tap screen to lock/unlock. Unlock not working
From Stock (ColorOS) Installation:
*Charge battery near full, DISCONNECT usb cable
Having the USB cable connected in this process causes hard to get out of bootloop after installation
1. Boot phone in fastboot mode: Press and hold both Power + Volume Up buttons.
2. Unlock boot loader with command: fastboot oem unlock
3. Flash recovery with command: fastboot flash recovery name.recovery.img
4. Reboot phone into recovery mode using command "fastboot reboot-bootloader" and press and hold Volume Down button.
5. Full wipe of device. Place ROM and Gapps on external SDcard or use ADB to transfer them to the (now wiped) internal Data partition.
6. Install ROM and GApps.
7. Reboot phone and wait (first boot will take quite a bit of time)
* If you don't have any previous experience with rooting, custom roms & recoveries. Please follow the more 'newbie' friendly in-depth tutorials
XDA forums has plenty of well done easy to follow tutorials!
From Lineage 14.1 :
*Charge battery near full, DISCONNECT USB cable before reboot into recovery
Having the USB cable connected in this process causes a hard to get out of bootloop after installation
*Make sure you have the latest TWRP recovery installed before continuing
1. Wipe device, perform a clean install
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)
NOTES:
*This is bat country! You are on your own when something goes bad, I can't help you in case of bricked device
*Precaution: Charge battery atleast 80%
*Advisable: Make Nandroid backup before flashing
*Precaution: Due to a weird device specific bug
Don't (re)boot into Recovery nor flash the R7 with the USB cable still attached. Could result in a bootloop which is rather hard to get out off
Bootloop trick: When finally powered off, leave the device off for at least a hour Take a walk or something!
No idea why but this seems to do the trick, after a prolonged period of being turned off, it boots normally into LineageOS
And will continue to reboot just fine! Maybe disconnect usb cable before rebooting out of precausion tho

Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?

Forage81 said:
Great work once again!
I assume this will be without the "project tremble" hardware separation layer introduced in Android Oreo, no?
With the differences in Android versions compared to stock, I do start to wonder, what are the drawbacks with this ROM? I mean in terms of performance, size, etc. Do you know of any?
Click to expand...
Click to collapse
Thank you!
Concerning Tremble, can't have 8.1 without but seems to be using legacy & updated vendor blobs.
Not sure what you mean with "stock" Stock AOSP 8.1 builds or the stock ColorOS?
Compared to stock ColorOS 4.4. too many differences to name. Compared to AOSP, I'd suggest reading into LineageOS features
Drawbacks to using this rom I can't think of one. Till now everything seems to be working just fine
Performance seems to be great, Battery life seems better than LineageOS 14.1 and concerning size it's smaller than stock ColorOS

I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?

I really hope
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.

Ravhinzy said:
I already test this rom.
It's really good.
I found the bug
1. Charging slow. Take 1 hour 45 mnite to full
2. Double tap to wake not work
I'm back to your previous rom 14.1
In Los 14.1 your build. Fast charging like vooc dan double tap to wake work.
Can u fix it?
Thanks somuch for great work.
Click to expand...
Click to collapse
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen

Forage81 said:
I believe tremble is mandatory for new phones and optional for existing that update to 8.1.
You would have known you are using Tremble if you are the one who created the port for this phone.
I don't believe you can just use existing blobs for a change like that and it would require help from Oppo, who had never offered even the slightest for our phone.
I meant Lineage OS 15.1 compared to stock Oppo/ColorOS. I know the differences OS/functionality wise. With such a big jump I would have expected at least performance issues since non of the blobs have been touched anymore. Decreased compatibility seems likely to me in such a case.
Good to hear you do not experience this.
I am hesitant to take the risk using this ROM though. For the same reasons mentioned above.
Have you been using the phone in real life without (too many) glitches for a bit by now?
Click to expand...
Click to collapse
Concerning your last question
Haven't turned my phone off since 7-5 while running this 15.1 build
Works great so far. Haven't found issues/glitches as of yet. No weird things happening with my daily usage thus far

-Oops things went a bit wrong-

JJRT said:
Both work fine in this 15.1 build
VOOC charging, and double tap @ statusbar/lockscreen
Must be something on your end. did you perform a clean install?
Wipe system,data,cache dalvik etc
But out of precaution I'll test it further in the coming days. More charging and more tapping on my screen
Click to expand...
Click to collapse
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it

Ravhinzy said:
Thanks for ur answers.
Oh. I will try it again. I always clean install like u said.
Double tap to sleep work fine in status bar or home botton. But to wake, all screen i taping, the phone not wake. Any ideas the problem?
I back to Los 14.1. all fine.
I really like u work on los 15.1. i want to use it
Click to expand...
Click to collapse
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option

JJRT said:
Ah indeed, the waking up using double tab isn't working atm.
I will look into that. The 15.1 build is perfectly usable otherwise.
But yeah you can roll back to 14.1 in the meantime if you really need the double tap option
Click to expand...
Click to collapse
Yes. I wait until the problem fix. And plis check charging time

Ravhinzy said:
Yes. I wait until the problem fix. And plis check charging time
Click to expand...
Click to collapse
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.

Forage81 said:
The charging time should not be impacted in any way as it is hardware based. Unless a ROM or app is using extreme resources while charging, draining the battery at the same time you are charging it, charging times should be the same in both 14.1 and 15.1.
Please double check if it has really changed.
Click to expand...
Click to collapse
Ok, thank you. I have returned to los 14.1. how to fix or replace double tap to wake to work? I want to try again. I will check it again

Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!

ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.

ph03nae said:
Wow amazing work!
I have checked that charging times are the same as los 14.1 as opposed to claims by Ravhinzy.
However, the issue of double tap to unlock is also present for all other screen off gestures (drawing O, M, V etc. when screen is off). Other than that, the roms seems stable enough. (so are u planning to make r7f rom official on lineage os?)
In any case, keep up the good work and thanks for sharing this rom!
Click to expand...
Click to collapse
Thank you
Yeah I can't replicate the charging issue as well. I have 2 R7f's laying around.
VOOC is working fine on both of them with my 15.1 build. Drained them both multiple times and recharged.
Still haven't figured out what the deal is with tap 2 wake.
The r7f will never get official lineageOS builds sadly because of the weird USB-attached on (re)boot bootloop bug

The link for the OS takes me to something called mega.nz but nothing loads, then it times out.

MrFlibble23123 said:
The link for the OS takes me to something called mega.nz but nothing loads, then it times out.
Click to expand...
Click to collapse
This rom is not for the r7plusf.

kishd said:
This rom is not for the r7plusf.
Click to expand...
Click to collapse
Good job I couldnt download it then, I'd have been scratching my head. The official Lineage page has a 15.1 nightly build but I can't get WiFi working on the device using it so have gone with 14.1

Ravhinzy said:
do you know how to fix dt2w?
eg with flash module or update.zip to fix it.
I've been looking for ways on google how to fix it still has not worked.
I really hope to get this cusrom. fell in love when first tried it.
Click to expand...
Click to collapse
New release, tape 2 wake should be functioning correctly now (I have tested it)

GSI images tested with POCO

I've tested 3 GSI images with my phone last weekend, here are the results:
--------------------------------------------------------------------------------------------------------------------------------------------------------------
1. PixelExperience: https://forum.xda-developers.com/poco-f1/how-to/treble-pixel-experience-9-0-t3839681
or here: https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
- Everything work well
- Feel faster than stock, no mi nonsense
- Wifi and data work fine
- Sound: OK
- Camera: work
- Bug: NO DARK MODE, it went black, and never come back.
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off
- I might do something wrong, but my bank app said the phone is rooted. So, I have to flash stock back.
2. LineageOS: https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
- There is this "privacy protection" error pop-up all the time
- Booted, run smooth
- Wifi and data work fine
- Sound and camera work.
- LineageOS handles the top and bottom curve better than PixelExp, the notification bar look better
- Some setting features were not working and follow with error, but the phone still work normally after error message
- I really hope the Lineage team get it work really soon. :good:
3. HavocOS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
- Bootloop...end
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Step
1. Unlock bootloader
2. Flash TWRP
3. With adb tool, flash system image (I've tried to flash PixelExp system image with TWRP, and got to bootloop, so I've changed to flash with adb command)
4. With TWRP flash decrypt
5. With TWRP wipe cache/dalvick
5. With TWRP format data
6. With TWRP flash decrypt again
Is there any way to flash PixelExperience without root?
PS. When I wrote that the camera work: I mean it works you can take a picture with both front and back cameras, but I didn't compare the picture quality at all.

Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it

Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?

I dont have any cut off on pixel experience after couple of reboots

Tomatot- said:
Thanks for your feedback, you will save us a lot of time!
So, so far, you haven't found any GSI that handle completely properly the notch and curves of our screen?
Click to expand...
Click to collapse
LineageOS handle the notch almost perfect, however, with other bug.

tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
It looks nice indeed! Thanks, I'll give it a try.

tomhtg90 said:
I dont have any cut off on pixel experience after couple of reboots
Click to expand...
Click to collapse
For me, the time and battery percentage are closer to the edge than yours.
Also, is it root? Can we flash without root?
Thanks.

kikoarl said:
Just tested Aosp Extended and I'll take the template you posted in the OP so it's easier for you.
AEX post: https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
- Rebooted itself a few times during the first boot.
- Felt sluggish during the first minutes, but then everything went smooth as butter.
- Wifi and data work fine
- Sound: OK
- Camera: work, but worse quality than stock
- Bug: NO DARK MODE, it went black, and never come back. In order to fix this you need to reflash the image
- Ugly: the notification bar is not so compatible with curve screen, the clock and battery percentage almost got cut-off. However you can almost fix it changing the display size, not a perfect fix but better than stock.
I'll be going to MIUI stock again, even though I hate it
Click to expand...
Click to collapse
I, personally don't have any preferred template.
It seems as if the AEX is more or less on par with the PixelEx.
Can you manage to flash it without root?
I can live with a bit ugly notification and some minor bug, but I need to use the bank app. So I want to flash it without root.

I tested RR v6.1 GSI and it works with 2 intolerable bugs.
1, 3.5mm headphone not works. Speaker still works when haedphone plug in.
2, since the notch removed by command 'wm size 1080x2074' (result:here), screenshots will add black frame on the top and bottom, and the original contents(1080x2274) are zipped into 1080x1902, so it looks a liitle strange
RR GSI post: gsi-resurrection-remix-o-6-1-0-t3811299
Flashed arm64 a only 0818 version.
- root(magisk 17.1) and xposed v90 beta3 work.
- Wifi and data(CMCC) work
- Sound: both speakers work
- Camera: work
- Bug: headphone not work , screenshot problem
although i hate MIUI , i have to return to it . i need 3.5mm. looking foward to lineage 15.1 or aosp, etc.

I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.

Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
I could answer that...easily...maybe
I hate MIUI.
I hate ads full rom.
I have high hope for the project treble, it's a good starting point for generic device rom.
I don't know about your development of the lineageos, this is the first post I saw this information.
Also, it's fun to try something, even not perfect, it's still fun to mess around.

Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
Thanks for the great news. And do you mind telling that you ve been watching the development where exactly?
Thanks once again.

Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.

$hivaM Manav said:
Tried 9.0 roms
1 Treblized os: very smooth and stable VOLTE problem.
2 Pixel experience: Smooth but thermal throttling is broken hearts up quite bit.
3 lineage os: doens't look as good as PE and yeah no VOLTE is any GSI 9 or 8.1
4 Arrow os: The best of all. Fast snappy.
5 Havoc os: Bootloop tried everything.
Tried 8.1 roms:
1 Arrow os: The best I must say. PUBG experience is great the touch is really snappy and accurate for some reason.
2 RR official: Has some weird issue maybe sound don't remember.
3RR unofficial: there were 2 unofficial builds one booted fine and the other got Bootloop. Sound was good in unofficial and boot animation is better.
4 Aquarius os: Simple and good.
5 Dot os: well I've tried this GSI on my OP5T it was amazing but in Poco it doesn't feel as stable as others.
After trying all these GSI roms the best stable snappy and thermal friendly ROM was 8.1 and 9 Arrow os.
Like if I helped you.
Click to expand...
Click to collapse
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?

Adios2nd said:
Wow, arrow os was not on my tested list. :good:
Need to try it asap.
Just question: can I flash it without root status?
Click to expand...
Click to collapse
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!

$hivaM Manav said:
Well I'm not sure because I flashed root on every GSI because my device feels uncomplete without it but I'm sure you won't have any problem with no root and yeah in some GSI roms we have option to download with gapps/su/ or vanilla
Edit:
I needed root access because I used this universal notch fix
Go to terminal give root access and type
"wm overscan 0,90,0,0" this completely pushes the notification panel below the notch and fits perfectly!
Click to expand...
Click to collapse
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?

Adios2nd said:
2 Questions
1. I didn't intend to flash root, but when I flashed the "Encryption disabler" (that every guides suggest to flash, see attached), it became root itself. Can I not flash it?
2. Do I need to fix the notch in ArrowOS, is it not detect and adjust by itself?
Click to expand...
Click to collapse
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.

The notch situation is a bit better in Lineage 9.0.
In every ROM, ir unlock doesn't work (as expected), and volte doesn't work (expected?!).
All cameras work well.
---------- Post added at 05:14 PM ---------- Previous post was at 05:14 PM ----------
Daruwalla said:
I'm not sure why everyone is so eager to test these GSI builds when they don't actually work 100% as stable.
LOS 15.1 development already in progress and I've been watching it, everything is looking good so far ( including camera, dual 4g/volte). Just give the devs sometime for the release.
Click to expand...
Click to collapse
mind posting the link?

$hivaM Manav said:
1. The encryption disabler is only for MIUI roms because it encrypts your data on first boot but GSI roms don't encrypt your data so you can skip flashing that after flashing GSI
2. Only Pie roms have the ability to adjust to notch currently this feature is not available in 8.1 roms so it'll look weird.
Click to expand...
Click to collapse
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
PS.
If I flash the GSI with adb fastboot, do I need to flash the encryption disabler?
(In fastboot, I do the "fastboot flash system GSI.img")

Adios2nd said:
I'm a very beginner so to flash without root:
0. Unlock bootloader
1. Flash recovery TWRP
2. In TWRP flash encryption disabler
3. Wipe (normal wipe?)
4. Reboot to recovery (Do I need this step?)
5. Flash GSI
6. Then reboot to system
Am I right?
Thanks for your answer.
Click to expand...
Click to collapse
One-time process:
1. UL bootloader.
2. Flash twrp.
3. Format user data for twrp dycript then reboot to recovery again without booting to os.
4. Flash encryption disabler boot once to os.
After this process you don't have to flash the encryption file again and again because it modifies your vendor partition for treble enable. You'll have to flash this file again after flashing any MIUI rom. If you need root in GSI you can flash this file or you can skip.

Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)

PREVIOUS VERSIONS:
Lineage 17.1 *UNOFFICIAL* for FIH (SAT/SS2/HH1/HH6/HD1/DRG)
Android 11 here: Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6) LEGAL https://lineageos.org/legal/ You flash this ROM on own risk! XDA:DevDB Information Lineage 17 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)...
forum.xda-developers.com
LEGAL
https://lineageos.org/legal/
You flash this ROM on own risk!
XDA:DevDB Information
Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
Multi ROM from sources supporting devices:
Sharp Aquos S2 4/64 -SS2/C10,
Sharp Aquos S2 6/128 -SAT,
Sharp Aquos S3 -sdm630 (HH1/HH6).
Sharp Aquos P6
Nokia x6 (DRG)
Contributors/Maintainers
heineken78
ROM OS Version: Android 11
ROM Kernel: 4.4
Recovery: TWRP 3.6.0 included.
Device sources: here
Gapps: Not included. Recommend to use only NANO version for normal functionality.
Data Encryption: encrypted;
Do not: use boot(twrp) or vendor with other older/stock roms.
Features:
-live display;
-lineage touch and mostly all hals available in Lineage support.
-adb root;
-safety net pass (with gapps installed);
-Google AR core support;
-Google Device Personalization Services;
Version Information
Status: Release
Created 2022-01-24
Last Updated 2022-01-24
Sources: https://github.com/Eddie07
DOWNLOAD:
GDRIVE FOLDER
Installation
1. First time
Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system.
2. Next updates/upgrades
Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.
Pls note: Due to changes in encryption, if you migrate from 17.1 version you will have to format data to be able to use newer roms.
TWRP backup from 17.1 is NOT COMPATIBLE with encryption of 18.1.
Bugs:
-Network manual selection -You will find may be
Communication channel in Telegram (English):
te.me/lossharpus
Please donate if you want to support my work.

reserved

Thanks Heineken.
You should propose your services to FIH as you have done more to support that device than their dev teams for last years
Appreciate your work to maintain our sharp phones uptodate with rock stable firmwares

Hi Heineken
Thanks for the new rom, I have upgraded with format data from your last 17.1 without problem.
With the 17.1 I had a bug the phone rebooted with a sony wh 1000 xmr3 now in 18.1 no problem
Since 2 days no problem battery life is good

Is it stable enough for daily use ?
@heineken78 you have wrote that:
LOS 18.1 almost on the way.
Its not so good as 17.1, but looks fine.
Could you please elaborate?
Do you recommend upgrade from 17.1 for daily use phone or I should still wait for newer 18.1 builds?

baszek said:
Do you recommend upgrade from 17.1 for daily use phone or I should still wait for newer 18.1 builds?
Click to expand...
Click to collapse
Im using 18.1 on regular basis.
Its up to you what you gonna use.

heineken78 said:
Im using 18.1 on regular basis.
Its up to you what you gonna use.
Click to expand...
Click to collapse
Your linage 17.1 version is really good - I am using it for quite a long time. If 18.1 version is the same, I will install it right now ;-). I saw that 18.1 has only two builds on your G drive, so I thought it might have still lots of bugs.

Hi Heineken!
First of all, thanks for an awesome rom!
I'm using it daily and i've found a few issues. The report:
-Flashlight is working, but camera apps can't use it in pictures (tried default one and google camera).
-Wired handsfree headphones behave erratic. If plugged in during a call, the call hangs. If previously plugged, sometimes work, sometimes don't. Tested with Panasonic and Xiaomi models.
-USB file transfer doesn't work.
Other than that seem actually great, tested WIFI, BT, GPS, sensors, etc everything fine. No LOS issues and very good performance.

@heineken78
I'm still using it daily, but lately dialer app is troublesome (freezes) and i need to reboot to get it working again.
Is this rom still active, or no new versions are planned?
In any case, than you for an awesome job!

pelitox said:
@heineken78
I'm still using it daily, but lately dialer app is troublesome (freezes) and i need to reboot to get it working again.
Is this rom still active, or no new versions are planned?
In any case, than you for an awesome job!
Click to expand...
Click to collapse
Hi I dont have this bug. Which dialer are you using?
Please post logs from device after rebooting after freezing from sys/fs/pstore folder in your device.
Due the war I have moved to another city in my country, Im planning to go on with development from my notebook.

heineken78 said:
Hi I dont have this bug. Which dialer are you using?
Please post logs from device after rebooting after freezing from sys/fs/pstore folder in your device.
Due the war I have moved to another city in my country, Im planning to go on with development from my notebook.
Click to expand...
Click to collapse
OMG! I didn't know you're ukranian!
I feel dumb for asking about rom support.
Take care, best wishes
About this bug, i think is related with previous message headset bug. I switched from wired to BT and this is not happening now.

awesome rom!! thanks a lot

Take care. Hope there is no war in the world

Hi, thanks for providing the lineage rom.
Sorry for the probably stupid question: I am unable to find a TWRP version for the aquos S3 and all the websites i found via google seemed very shady. (So far I only had phones for which TWRP was readily available)
I know it says included, but in the installation instructions it says to boot directly into TWRP? So i guess it has to be installed before?
Any hints where I could find one?

自由类者 said:
Take care. Hope there is no war in the world
Click to expand...
Click to collapse
There isn't anymore "war", there are "special operations"
chocobear said:
Hi, thanks for providing the lineage rom.
Sorry for the probably stupid question: I am unable to find a TWRP version for the aquos S3 and all the websites i found via google seemed very shady. (So far I only had phones for which TWRP was readily available)
I know it says included, but in the installation instructions it says to boot directly into TWRP? So i guess it has to be installed before?
Any hints where I could find one?
Click to expand...
Click to collapse
Take the boot image from the Heineken LOS archives and flash or boot it. Recovery is actually in the boot image for A/B systems. You can find all inputs about flashing and booting TWRP in the other Heineken threads.

Psyl0w said:
Take the boot image from the Heineken LOS archives and flash or boot it. Recovery is actually in the boot image for A/B systems. You can find all inputs about flashing and booting TWRP in the other Heineken threads.
Click to expand...
Click to collapse
Thanks, I'll have a look!

Does anyone know what type of battery I can use for sharp aquos S2 C10 ?
Can I use as a replacement HE332 battery ?
I saw that heineken was using some battery from Nokia, which can replace original battery
https://www.aliexpress.com/item/32995443415.html?spm=a2g0o.productlist.0.0.3504779cYDTxJY&algo_pvid=320056ae-8873-4644-89a2-4a30022fab10&algo_exp_id=320056ae-8873-4644-89a2-4a30022fab10-0&pdp_ext_f=%7B%22sku_id%22%3A%2266889130643%22%7D&pdp_npi=2%40dis%21USD%21%2113.47%21%21%21%21%21%402100bb5116577339026963577eafb4%2166889130643%21sea

baszek said:
Does anyone know what type of battery I can use for sharp aquos S2 C10 ?
Can I use as a replacement HE332 battery ?
I saw that heineken was using some battery from Nokia, which can replace original battery
Click to expand...
Click to collapse
Yes HE332 battery is fine. Just check the quality of the battery as lot of failing products are sold on aliexpress.
Opening the phone is easy if you follow Heineken video. Be careful to not hang flex cables on the upper part of the device but the bottom side and around the battery is ok. (see attached pic)
Taking out the old battery is painful as the tape is very strong against tearing off.
Setting up the new battery is easy except the handling of the rubber tape.
I sealed the box with neoprene glue.

Psyl0w said:
Yes HE332 battery is fine. Just check the quality of the battery as lot of failing products are sold on aliexpress.
Opening the phone is easy if you follow Heineken video. Be careful to not hang flex cables on the upper part of the device but the bottom side and around the battery is ok. (see attached pic)
Taking out the old battery is painful as the tape is very strong against tearing off.
Setting up the new battery is easy except the handling of the rubber tape.
I sealed the box with neoprene glue.
Click to expand...
Click to collapse
I thought that C10 version has got some different battery type. Do you think that this HE332 from alliexpress is legit ? According to AccuBattery right now my battery health is 75% = 2201 mAH

C10 is the European flavor and the rated capacity is specified: 2900mAH
S2 sharp claims the typical capacity: 3000mAH but I think the battery is the same. You can open the housing if you want to check.
2200 mAH is still not bad. Mine was totally dead (cannot be charged). I bought from that seller https://www.aliexpress.com/item/400..._list.0.0.21ef5e5b3ROMbl&gatewayAdapt=glo2fra
I cannot assure it's an orignal battery but it powers my mobile for longer than 1 day.
The pic I posted previously shows the battery from that seller but keep in mind Chinese are very good to copy even the packaging