[CLOSED][ROM][7.1.2][2018-09-26] UNOFFICIAL LineageOS 14.1 for ASUS MeMO Pad 7 (ME176C(X)) - MeMO Pad 7 Original Android Development

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
NOTE: LineageOS 14.1 is no longer updated. Consider using LineageOS 16.0 instead.
About this project
This is not a regular ROM. Usually, ROMs are based on certain components of the stock system (e.g. the kernel and certain proprietary components). This is a completely new ROM with a new Linux kernel and new implementations for all system components. It is not goal of this project to reach full hardware support or to make it perfectly stable. I will try my best, of course, but I mostly see this as a research project for myself to see how much you can implement with open-source components.
New features
Android 7.1.2 (LineageOS 14.1) with latest security patches
Linux 4.14 kernel
Vulkan graphics (experimental)
Less/no bloatware
Full backlight control (allows much lower brightness)
F2FS (with a compatible recovery)
USB OTG
Rootless Substratum theme engine
Signature spoofing (allows using MicroG instead of proprietary Google Play Services)
WireGuard
Tested features
Everything not mentioned here is likely not working.
Device boots
Graphics (OpenGL etc)
Charging
WiFi
Sound (Speaker + Headphones), Microphone (quality is pretty bad though...)
Bluetooth (incl. Bluetooth Audio (A2DP))
Accelerometer (used for device rotation), magnetometer (needs verification that it is reporting values correctly)
Backlight control
SD Card
Hardware video acceleration (experimental)
DRM (e.g. for Netflix and other streaming apps, experimental)
Full disk encryption
Planned features (not working yet)
Suspend/Deep sleep states
Not planned
Camera: See issue #47 on GitHub
GPS: See issue #48 on GitHub
FAQ
How is the battery live? Screen-on time is probably similar if not longer, but there is a lot of battery drain in standby mode (even worse than on the ASUS system). I recommend that you turn off the tablet when you're not using it.
How do I obtain root access? There are various ways, but the recommended way for LineageOS is to flash addonsu. For some reason Lineage's x86 addonsu isn't working correctly. Download and flash addonsu-14.1-me176c-signed.zip instead. However, note that this will break SafetyNet. Use Magisk alternatively.
Can I use Netflix with this ROM? Yes.
Installation
Preparation
Make sure you are running Android Lollipop (5.0).
You need an unlocked bootloader. The recommended bootloader is me176c-boot, but in case of problems you can also use the older bootloader.
Install TWRP. I recommend downloading the latest version of TWRP from the separate thread.
Make a full backup of the ASUS system. You may want to go back to it.
Do a full factory reset. Wipe data and cache partitions.
Install the ZIP provided below.
Download
System image (install as ZIP in recovery): lineage-14.1-20180926-UNOFFICIAL-me176c-signed.zip
TWRP recovery image: Available in a separate thread.
Optional: Download Google apps (x86 for Android 7.1): Open GApps
Optional: Root access: addonsu-14.1-me176c-signed.zip (Magisk is also working if you prefer that)
Optional: Custom build of Xposed that doesn't cause boot loops: xposed-v89-sdk25-x86-me176c-signed.zip (flash it in recovery)
XDA:DevDB Information
Unofficial LineageOS for ASUS MeMO Pad 7 (ME176C(X)), ROM for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2017-07-07
Last Updated 2020-05-12

Version History
Available on GitHub.

Omg, just wow, finally a custom rom, ill flash it asap

Just flashed the rom an hour ago, had some issues with rotating screen which i fixed by installing an app that manually changes screen rotation.
I also enabled a toggle from notifications that allowed me to set either the heaphone or the speakers.
The rom feels a lot smoother than ZenUI and I was able to install substratum and put a theme, worked just fine, I also installed magisk but unfortunately certification doesnt work.
Also Netflix says its not compatible on the playstore, and when trying to install the apk, it allways says its incompatible with the tablet. Another issue i found was that the sound sometimes makes a weird sound (more noticeable when using headphones).
The wifi seems to turn off while suspended, even if its set to not turn off while suspended.
Other than that, rom seems pretty good. Keep up the good work

Ruben Craveiro said:
Just flashed the rom an hour ago, had some issues with rotating screen which i fixed by installing an app that manually changes screen rotation.
Click to expand...
Click to collapse
As mentioned in https://github.com/me176c-dev/device_asus_me176c/issues/7, I had the issue that the accelerometer (which is used for device rotation) doesn't report any data after a restart. However, when I turned off the tablet, waited a few seconds and then turned it back on it worked fine. Can you try that?
Ruben Craveiro said:
I also enabled a toggle from notifications that allowed me to set either the heaphone or the speakers.
Click to expand...
Click to collapse
I have added a custom quick settings tile as part of the ROM that can be used to toggle speaker and headphones. That's the recommended way to switch between them (or is that what you mean with "toggle from notifications")?
Ruben Craveiro said:
I also installed magisk but unfortunately certification doesnt work.
Click to expand...
Click to collapse
Not sure, I've never used that...
Ruben Craveiro said:
Also Netflix says its not compatible on the playstore, and when trying to install the apk, it allways says its incompatible with the tablet.
Click to expand...
Click to collapse
Netflix is blocked for rooted devices using SafetyNet so it's correct that it's not displayed in the Play Store. However, even if you'd manage to install it on the tablet it wouldn't work because the required DRM libs aren't included currently. That's another proprietary mess I need to add (but it's a bit complicated because the original libs are not always perfectly compatible with the new kernel version etc.)
Additionally, if a APK is reported to be incompatible it's possible that it includes native libraries only compiled for ARM. That's mostly because some developers ignore (or used to ignore, it's less frequently now) the x86 architecture because there are not too many devices using it. Intel's solution for that is a proprietary translation layer called Houdini, which is not yet included in the ROM.
Ruben Craveiro said:
Another issue i found was that the sound sometimes makes a weird sound (more noticeable when using headphones).
Click to expand...
Click to collapse
Have you disabled touch sounds? I've noticed that these cause weird issues quite frequently. Not sure what's causing them.....
Ruben Craveiro said:
The wifi seems to turn off while suspended, even if its set to not turn off while suspended.
Click to expand...
Click to collapse
That's weird because there is no suspend at all currently (the tablet will stay on the whole time). It might be some kind of power saving feature. I will try to reproduce that.
Ruben Craveiro said:
Other than that, rom seems pretty good. Keep up the good work
Click to expand...
Click to collapse
Thanks

lambdadroid said:
As mentioned in https://github.com/me176c-dev/device_asus_me176c/issues/7, I had the issue that the accelerometer (which is used for device rotation) doesn't report any data after a restart. However, when I turned off the tablet, waited a few seconds and then turned it back on it worked fine. Can you try that?
I have added a custom quick settings tile as part of the ROM that can be used to toggle speaker and headphones. That's the recommended way to switch between them (or is that what you mean with "toggle from notifications")?
I also installed magisk but unfortunately certification doesnt work.
Not sure, I've never used that...
Not sure, I've never used that...
Also Netflix says its not compatible on the playstore, and when trying to install the apk, it allways says its incompatible with the tablet.
Netflix is blocked for rooted devices using SafetyNet so it's correct that it's not displayed in the Play Store. However, even if you'd manage to install it on the tablet it wouldn't work because the required DRM libs aren't included currently. That's another proprietary mess I need to add (but it's a bit complicated because the original libs are not always perfectly compatible with the new kernel version etc.)
Additionally, if a APK is reported to be incompatible it's possible that it includes native libraries only compiled for ARM. That's mostly because some developers ignore (or used to ignore, it's less frequently now) the x86 architecture because there are not too many devices using it. Intel's solution for that is a proprietary translation layer called Houdini, which is not yet included in the ROM.
Another issue i found was that the sound sometimes makes a weird sound (more noticeable when using headphones).
Have you disabled touch sounds? I've noticed that these cause weird issues quite frequently. Not sure what's causing them.....
Have you disabled touch sounds? I've noticed that these cause weird issues quite frequently. Not sure what's causing them.....
The wifi seems to turn off while suspended, even if its set to not turn off while suspended.
That's weird because there is no suspend at all currently (the tablet will stay on the whole time). It might be some kind of power saving feature. I will try to reproduce that.
Thanks
Click to expand...
Click to collapse
I would problably use it as my main os, but not being able to install netflix is whats keeping me from staying here, i hope you can fix it, and the sound issues, if both features are fixed ill use it since i only use the tablet for music and netflix

Ruben Craveiro said:
I would problably use it as my main os, but not being able to install netflix is whats keeping me from staying here, i hope you can fix it, and the sound issues, if both features are fixed ill use it since i only use the tablet for music and netflix
Click to expand...
Click to collapse
Sure. I will put it on my list, but it requires a substantial amount of work due to the amount of proprietary libraries required to make it working. Could you clarify what issues with sound you have? I know that the touch sounds cause weird beep sounds and I know that there is some noise when switching from headphones back to the speaker. It works fine for me otherwise.

lambdadroid said:
Sure. I will put it on my list, but it requires a substantial amount of work due to the amount of proprietary libraries required to make it working. Could you clarify what issues with sound you have? I know that the touch sounds cause weird beep sounds and I know that there is some noise when switching from headphones back to the speaker. It works fine for me otherwise.
Click to expand...
Click to collapse
On youtube app, when in headphone mode sometimes theres static sound but no actual sound, the app needs to be reopen multiple times for it to actually start playing, and the beep sound doesnt just happend to the "touch sounds", it seems to happend when the device gets hot/starts to trottle(i might be wrong but its what it seemed that was happening).
Edit: Any other issues i find, ill just post on your github

I'll be flashing this when I get home. This will definitely be my daily driver once charging is tested a bit more and the battery drain is resolved.

Thank you so much for a custom rom for this device!
I also formatted data and cache partition to f2fs with your twrp build.
It's incredible fast and stable enough for my use (internet, xda'ing, facebook and youtube)
It's my daily driver for now on even with these little bugs. But I don't care if these bugs still appears, the most important things works and I'm very happy.
And in my opinion, the battery life is better and the device gets less hot then the asus rom
Thank you so much!!
ROM passes safetynet with magisk v13.1, magisk hide enabled and the universal safetynet fix v2 beta 4 from Deiki installed.
Little (cosmetic)"bugs that aren't reported yet:
- Used storage capacity is negative and comes closer to zero when you fill up the space.
- It also shows 7,43 GB of total space on a 16 GB variant.
- My external sd card gets a strange name in settings and on the system file manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks Dude for this custom rom!
I´ll try tomorrow and the 3D games works?
there is [Benchmarks] File System Performance: F2FS vs EXT4
https://forum.xda-developers.com/showthread.php?t=2697069

Hi everyone. Will this ROM work with my ASUS Memo Pad 7 (Model: K013, Firmware: WW-3.1.23.158, Ru Version)? Thanks a lot!

Mystmuse said:
Hi everyone. Will this ROM work with my ASUS Memo Pad 7 (Model: K013, Firmware: WW-3.1.23.158, Ru Version)? Thanks a lot!
Click to expand...
Click to collapse
If you are running Android Lollipop (5.0) and you have unlocked bootloader (and obviously have TWRP), You can!

jerbear294 said:
I'll be flashing this when I get home. This will definitely be my daily driver once charging is tested a bit more and the battery drain is resolved.
Click to expand...
Click to collapse
As far as I can tell, charging is working fine. I've tried it again in the last days and it charged correctly, even quite quickly. I should note that I've only tested using the original ASUS AC adapter, though. Normally, charging should behave exactly the same as on the original ASUS system. (It's the same driver, just with a lot of cleanup) Unless someone else finds a problem I'll probably leave it as-is.
(At this point I should mention that ASUS charging driver is horrible, it's extremely messy and looks like it was stuffed together and never finished. There were over 2k lines of code which weren't doing anything (because they are never reached) and a lot of spammy debugging output that wasn't removed. I wouldn't be surprised if it breaks in some cases, but that is likely not my fault...)
I definitely need to work on the battery drain but the suspend procedure is quite complex on this tablet: Normal PCs usually save power by powering off all components, and only keeping the RAM alive in a low power states (suspend to RAM). That doesn't exist on Bay Trail tablets, instead there are so-called S0ix power states in which the CPU and other components enter a low-power state (but the network connection is kept alive for example). I have not been able to figure out how to make the tablet enter one of the S0ix power states. It seems like certain preconditions are required (e.g. display is powered off) but there is no clear documentation on this.... I will need to take a closer look when I'm back from vacation.
Nexive said:
- Used storage capacity is negative and comes closer to zero when you fill up the space.
- It also shows 7,43 GB of total space on a 16 GB variant.
Click to expand...
Click to collapse
That's quite funny. It doesn't happen for me, but on the other hand it somehow shows a total storage of 29 GB for me... (It has only 16 GB) I'll look into this soon.
Edit: It seems like it is influenced by the external SD card. Does your external SD card have a size of 8 GB? When I removed it and rebooted it showed the correct internal storage. (My SD card is 32 GB so it previously showed something close to the size of my external SD card)
Nexive said:
My external sd card gets a strange name in settings and on the system file manager.
Click to expand...
Click to collapse
That's weird! It works for me. Is your external SD card formatted using FAT32? You may want to try to format the SD card directly on the tablet (make sure to backup the files first), looks a bit like some kind of encoding problem.
bryandroid98 said:
Thanks Dude for this custom rom!
I´ll try tomorrow and the 3D games works?
Click to expand...
Click to collapse
3D stuff should work (even with more OpenGL/Vulkan features supported) but my tests have shown slightly lower performance than on the original ASUS system.

lambdadroid said:
That's quite funny. It doesn't happen for me, but on the other hand it somehow shows a total storage of 29 GB for me... (It has only 16 GB) I'll look into this soon.
Edit: It seems like it is influenced by the external SD card. Does your external SD card have a size of 8 GB? When I removed it and rebooted it showed the correct internal storage. (My SD card is 32 GB so it previously showed something close to the size of my external SD card)
That's weird! It works for me. Is your external SD card formatted using FAT32? You may want to try to format the SD card directly on the tablet (make sure to backup the files first), looks a bit like some kind of encoding problem.
Click to expand...
Click to collapse
Yes it was formatted as FAT32 and my external SD card is indeed 8GB. And like you said, I removed the card, rebooted my device and it shows the correct storage as long there is no SD card in the tablet.
This little bug is just ''cosmetic'' and is not that important so I don't care if it excist or not. This rom is already so much better for me than the asus rom so thanks again for this wonderful rom. :victory:
I also formatted my external SD card (on an other device because I got a timeout when I tried to format it on the me176cx) and got a normal name now for my external SD card.

Can I use Netflix on this rom?

bryandroid98 said:
Can I use Netflix on this rom?
Click to expand...
Click to collapse
nope, tried that already

I just install it (ME176CX), is working very nice thank you.

This is amazing. Thank you.

Is this going to get further development? It sounds very promising!
Thanks!

Related

Huawei Ascend D1 Quad XL (U9510E) - Update to Jelly Bean 4.1.2

Hello Everyone,
Below is a tutorial I have compiled and translated from bbs.anzhi.com on how to update your Huawei Ascend D1 Quad XL (U9510E) to the latest version of Android offered by EmotionUI, Jelly Bean 4.1.2:
First of all, I want to give credit where credit is due:
genokolar (aka G大) - Creator/Modder of the Custom Recovery for this, and many other phones coming out of China
Ry09iu (aka R大) - Creator of a Rooted ROM based on EmotionUI B534, which is based on Android 4.1.2
【LUV】 - The board moderator for the D1Quad section of bbs.anzhi, also who's ROM release I used for my phone, but it's upto you to choose which one you want to use
**IT IS NOT RECOMMENDED FOR YOU TO ATTEMPT THIS IF YOU DO NOT HAVE A PREVIOUS EXPERIENCE WITH FLASHING PHONES. IN THE CHANCE THAT YOU BRICK YOUR PHONE, I CANNOT BE HELD RESPONSIBLE FOR IT**
**DON'T FORGET TO BACKUP YOUR FILES!!**
Now that the credits and the warning are given, let's get started:
Required Tools:
1. Recovery 6.0.1.9: This tool will open in command prompt and will allow you to flash in the Custom Recovery created by genokolar, as well as the stock recovery released by Huawei. Mirror
2(a).Official ROMs:
i. Official EmotionUI ROM B551 (Updated January 11, 2013): Release Notes​
2(b).Custom ROMs:
i. Rooted Version of EmotionUI Rom (Author: genokolar):
- B534 Download​
ii. Rooted Version of EmotionUI Rom (Author: Ry09iu):
- B534 Download
- B538 Download​
iii. Rooted Version of EmotionUI Rom with HOLO as default Launcher (Author: Ry09iu, Modded by LUV):
- B534 Download
- B538 Download
- B542 Download​
iv. MIUI V4.1 - converted from MIUI V4.1 for Honor 2 (Author: Ry09iu):
- Download​​
3. GApps [Jelly Bean 4.1.2 (Author goo.im/gapps)]: Download
*The roms are hosted in China so the download will be slow, please be patient and your download will be done in an hour or two *
**PLEASE PLACE THE ROM YOU WISH TO UES INTO YOUR EXTERNAL SD CARD BEFORE CONTINUING**
Step 1: Flashing Custom Recovery
1. Turn-on USB debugging on your phone [Settings -> Developer Settings -> USB debugging]
2. Plug in your Phone to your computer via USB for it to install the appropriate drivers*
3. Run recovery6.0.1.4_AscendD1Q.exe
3.5 If your system locale is set to anything other than Chinese, you will get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But what you should see is this:
What that means is: said:
**-1. Flash Chinese Custom Recovery-**
**-2. Recover Official Recovery-**
##-3.Reboot phone into Recovery-##
Click to expand...
Click to collapse
4. Type in "1" and press Enter -> This Recovery Flasher will do what it's made to do and when it's completed, your phone will now have a custom recovery.
5. The application will automatically close 10 seconds after the Recovery has been successfully flashed.
Note from Genokolar said:
1. The development of this Custom Recovery was done through email with Huawei so it may be lacking certain features, a full custom recovery will be released as soon as responds him
2. This recovery will only flash from an external SD Card, internal SD card flash is not yet supported
3. At the time of this Custom Recovery being posted, no third-party ROM has been released, therefore it has not been tested <- No longer the case
4.This recovery can be used to Root the EMUI ROMs released by Huawei
5. When you need to flash back to the original ROM releases by Huawei, or receive OTA updates from Huawei, please flash back the original Recovery
Click to expand...
Click to collapse
*If the drivers do not install properly, please download the driver attached in this post and install it manually.
Step 2: ROM Flashing
1. Boot your phone into the new recovery. (either by starting the application again and selecting option 3, or press and hold the Power Button with Volumn Up)
2. You will be greeted by the Custom Recovery Screen show below:
[*] Reboot system now
[*] Select zip to flash/install
[*] Wipe data
[*] Wipe cache
[*] Backup and restore
[*] Flash memory/Format
[*] Advanced setting
[*] Turn off phone
Click to expand...
Click to collapse
3. Scroll to select option 3 (Wipe data), confirm the wipe
4. Scroll to select option 4 (Wipe cache), confirm the wipe as well
5. Scroll to select option 2 (Select zip to flash/install)
[*] Select zip from SD Card to Flash
[*] Install /sdcard/update.zip
[*] Activate/Deactivate Signature Verification
[*] Install from external zip
<-- Back to previous screen
Click to expand...
Click to collapse
6. Scroll to and select option 4 (Install from external zip)
7. Scroll to and select the zip file of the ROM which you have previously downloaded and placed into your external SD Card, confirm the flash
7.5. At this point, you can either flash in the gapps right away, or flash it after rebooting into the OS. I chose to flash it after booting into the OS for the first, but I don't think it will cause any problems. I will be posting the way I did it, and if you guys did it the other way, let us know if it worked or not
*IMPORTANT NOTE*
When you're booting up your system out from Recovery, you will be asked whether or not you would want your ROM to auto update the recovery, shown below:
[*] Yes - Forbid Auto Update of Recovery
[*] Cancel - Back
<-- Return to previous
Click to expand...
Click to collapse
Please select the one being highlighted in the image, which is option 2 ([*] Cancel - Back). OR CONSEQUENCES WILL NEVER BE THE SAME!
Step 3: Flashing GApps
1. Boot into recovery
2. Scroll to and select option 4 (Install from external zip)
3. Scroll to and select the zip file of GApps you have downloaded "gapps-jb-20121011-signed.zip" or whatever you may have renamed it to, confirm the flash
4. Reboot into OS
5. *THE NOTE ABOVE STILL APPLIES, SO HERE IT IS AGAIN*
*IMPORTANT NOTE*
When you're booting up your system out from Recovery, you will be asked whether or not you would want your ROM to auto update the recovery, shown below:
[*] Yes - Forbid Auto Update of Recovery
[*] Cancel - Back
<-- Return to previous
Click to expand...
Click to collapse
Please select the one being highlighted in the image, which is option 2 ([*] Cancel - Back). OR CONSEQUENCES WILL NEVER BE THE SAME!
Click to expand...
Click to collapse
Step 4: ALL DONE!
Congratulations, assuming everything was done properly, and everything worked out, now you will have Android 4.1.2 on your Huawei Ascend D1 Quad XL.
Images not showing up in your GooglePlay Store? YouTube not working?
Here is how our very own 12andy fixed the problem:
12andy said:
UPDATE: So using a clear hosts breaks the ability to connect to Facebook (via app and website). It's best to use AdAway, instead.
Nvana, it's the same process we've been using to flash the Chinese ROM(s), but with the added step of "fixing" the hosts file:
download SmartHosts from Goole Play (free)
tap on "Toggle hosts file" button
select "Clean hosts file"
And you're done! Rebooting wasn't necessary either, as the images started loading immediately.
Click to expand...
Click to collapse
Thank you for translating this! I do have a several question though.
1) Is it possible to edit the recovery so we can implement English into it? Maybe you can collaborate with the dev that made the recovery and ask him to make an English version of it??
2) I did a little research and I think the Chinese ascend is u9508 where ours u9510e. would there be any conflict or some features not usable?
3) I know you can change the system language but I am just wondering is there any difference in the chinese version of 4.1 vs the english version? or its just simply a language pack thing?
Wish you were in the 'GVA'
Thanks for doing this! Hope more people can test it out. I am bit too busy to play with my phone now so I'll do it in a week or so!
Keep up the good work!
nvana said:
Thank you for translating this! I do have a several question though.
1) Is it possible to edit the recovery so we can implement English into it? Maybe you can collaborate with the dev that made the recovery and ask him to make an English version of it??
2) I did a little research and I think the Chinese ascend is u9508 where ours u9510e. would there be any conflict or some features not usable?
3) I know you can change the system language but I am just wondering is there any difference in the chinese version of 4.1 vs the english version? or its just simply a language pack thing?
Wish you were in the 'GVA'
Thanks for doing this! Hope more people can test it out. I am bit too busy to play with my phone now so I'll do it in a week or so!
Keep up the good work!
Click to expand...
Click to collapse
Hey no problem at all,
1) I will suggest that to him, no problem, but not sure if he's willing to accept it though, but I'll try
2) The U9508 is actually the Honor 2, not the same as the D1 Quad XL. The Honor 2 was designed as a high powered budget ranged device to counter the XiaoMi M2 and the D1 Quad XL was supposed to be their flagship device. Although there is actually a Honor 2 with 2GBs of ram though lol
So to answer your question, this was made specifically for our phone the U9510E
3) Huawei has not yet released an international version of the EmotionUI for our phone, so the only way to get Jelly Bean on our phones is to run the Chinese version of the ROM. And to be honest, there aren't any major differences. For example, one difference is that the Chinese version will not have the Google apps, but we can patch it in by flashing the gapps from goo.im. I think the only difference would be that the international versions will have more language support.
Haha no problem, let me know when you do get to try it out
I've tried it many times however it did not work. The connection to the Chinese server seems to be established, unfortunately the ROM download did not start.
Got JB up and running late last night!
Please see my notes below.
ROM download:
make SURE that the ROM you download is in ZIP format; the recovery does NOT recognize 7z files (as expected)
for this reason, I downloaded version B
use Flashget to grab the file (saves a lot of time and grief in the event of network disconnections)
Flashing Custom Recovery:
the phone's drivers MUST be installed first
I think the program must be run first as well, prior to plugging the phone in (the procedure would only work once I toggled my phone from Mass Storage to Hi, and back to Mass Storage again)
Flashing GApps:
I flashed GApps right after flashing the ROM, but my phone sat at the Huawei logo even after multiple reboots
I went back into Recovery and performed a wipe, which fixed the problem
upon booting, I only had to install Gmail; Play Store was intact, and might've been included with the ROM already
ROM Impressions:
language selection was one of the first screens shown, so that part was very straightforward
don't know if it's a JB thing, but scrolling performance has improved irrespective of performance setting - smoother, with less input delay (say, scrolling up and down very quickly)
camera UI slightly changed (cleaner, perhaps?); continuously auto-focuses as you move the phone, so hitting the shutter "button" results in near instantaneous response (cool!)
more notification bar toggles - can be rearranged to a certain point
themes implementation - not really a fan of this, as I prefer the stock Android look/ feel for the most part; choice of vanilla Android is available
lock screen shortcuts can only be modified if using a theme
stock SMS client isn't vanilla Android - looks nicer, but isn't as responsive IMO
menu/ submenu background is near white - probably a bug, as white text on a near white background is just painful; probably not great for battery life either, and is not consistent with ICS+ Android colours
Dropped by the Chinese forum (yay for Chrome auto-translate!) to see if I can decipher any pending updates, but to no avail, lol. Looks like these ROM authors are also focusing on optimizations as well - happy to see that.
REALLY hoping this phone gets more popular very soon, and receives the Cyanogenmod 10 treatment.
Many thanks, Simon! Any chance you could convince the ROM authors over there to volunteer to become CM10 maintainers for our phone?
-AdMiRaL- said:
I've tried it many times however it did not work. The connection to the Chinese server seems to be established, unfortunately the ROM download did not start.
Click to expand...
Click to collapse
Hmm, what browser are you using? I noticed that my Chrome sometimes had problems loading the site because of the extensions I was using, maybe try it again in IE?
12andy said:
Got JB up and running late last night!
Please see my notes below.
ROM download:
make SURE that the ROM you download is in ZIP format; the recovery does NOT recognize 7z files (as expected)
for this reason, I downloaded version B
use Flashget to grab the file (saves a lot of time and grief in the event of network disconnections)
Flashing Custom Recovery:
the phone's drivers MUST be installed first
I think the program must be run first as well, prior to plugging the phone in (the procedure would only work once I toggled my phone from Mass Storage to Hi, and back to Mass Storage again)
Flashing GApps:
I flashed GApps right after flashing the ROM, but my phone sat at the Huawei logo even after multiple reboots
I went back into Recovery and performed a wipe, which fixed the problem
upon booting, I only had to install Gmail; Play Store was intact, and might've been included with the ROM already
ROM Impressions:
language selection was one of the first screens shown, so that part was very straightforward
don't know if it's a JB thing, but scrolling performance has improved irrespective of performance setting - smoother, with less input delay (say, scrolling up and down very quickly)
camera UI slightly changed (cleaner, perhaps?); continuously auto-focuses as you move the phone, so hitting the shutter "button" results in near instantaneous response (cool!)
more notification bar toggles - can be rearranged to a certain point
themes implementation - not really a fan of this, as I prefer the stock Android look/ feel for the most part; choice of vanilla Android is available
lock screen shortcuts can only be modified if using a theme
stock SMS client isn't vanilla Android - looks nicer, but isn't as responsive IMO
menu/ submenu background is near white - probably a bug, as white text on a near white background is just painful; probably not great for battery life either, and is not consistent with ICS+ Android colours
Dropped by the Chinese forum (yay for Chrome auto-translate!) to see if I can decipher any pending updates, but to no avail, lol. Looks like these ROM authors are also focusing on optimizations as well - happy to see that.
REALLY hoping this phone gets more popular very soon, and receives the Cyanogenmod 10 treatment.
Many thanks, Simon! Any chance you could convince the ROM authors over there to volunteer to become CM10 maintainers for our phone?
Click to expand...
Click to collapse
Great to see that everything worked! I hated their custom UI too, that's why I opted for HOLO Launcher HD for the stock JB feel
Supposedly Huawei will be working with genokolar to fully unlocked the bootloader and release a full custom recovery sometime this week so that should open up doors for other developers
And I don't even think they'll need any convincing, this thread here is a member of their development team releasing CM10 for the Ascend P1, so it's just a matter of time!
You're welcome
simonfzhao said:
Hmm, what browser are you using?
Click to expand...
Click to collapse
I tried to download via firefox however with using flashget as pointed out by Andy the download started immediately, for whatever reason.
I am also sure that this phone gets most popular soon because of a successfull compromise - strong battery, most compact size ( one-hand operation), 4,5" IPS+ display, quad core cpu and microSD. So keep your fingers crossed that our phone gets their own forum.
I do hope we get our own page but the thing that is stopping this phone from getting popular are
1) Hard to get your hand on one (BIG ISSUE)
2) Too late to join the quad core market (most people on S3 already and another big issue i mean who in their right mind is gonna give up s3 for this? and you can get a used S3 or BNIB for almost the same price of this phone if you try to import it...)
3) Try to ask anyone if they know what Huawei is ... most-likely they will be like `"what and where" ;p
4) This phone seems to be more appealing to the minority which are us who like to mess around and install Roms... and mess around during the day and runs out of battery (one reason why I choose GNex over many other great phone and one time i flashed 2 different Rom in one day at school because i was bored and then ending up running out of battery).
Yeah i hope their next phone would really make a dent in the market! But for now they already missed their chance to speak up and choose to forever hold their peace...
Well anyways while I am blah blah ing i just finished Downloading the Rom using Chrome, No Problem and took me less then 30 min. Well report back after i flash... which I should be studying for finals but... just cant stand the temptation you guys are posting....
Edit: Rom option 2(b)
So I got the rom to install but are faced with a few issue
1)*solved* Boot animation sound, I am ok with the boot animation but i dont like having sound... Would fast boot wolve that? or it takes the whole boot animation off? (Apparently if you turn the phone off in silent it will not make a sound when you turn it on!)
2) Play store not showing any image... I am not quite sure why... (Google it and did everything possible and still no avail...)
3) Messaging app when i type the keyboard cover the messages, like the message doesn't auto move above the keyboard and when i scroll the keyboard goes away. ** minor issue but its frustrating...
4) I just noticed I can't access YouTube from both the apps and the browser. Does this have to do with the rom?
I agree, this phone needs to be marketed much more here; bit of a dark horse, if you ask me.
Your S3 claim: I would have to slightly disagree with you on that one. Most people I know are still rockin' the iPhone and/ or Blackberry (this is a dying breed, however), but the tides are slowly changing now, as people are starting to take notice of Android. I only know three people with S3s, one person with a Note 2, and another recently obtained a Nexus 4 (had his Blackberry for awhile).
Boot animation sound:
I had my phone on silent (well, vibrate) last night, but the sound played still upon rebooting(?). Will test further.
Play Store images:
At first I thought it was my internet connection messing up, but turns out this is not the case. The first Google result pointed me to this, which indicates that using SetDNS (and choosing an appropriate DNS server - I like Google's/ OpenDNS', personally) solves the problem. I'll try this over lunch time at work.
Messaging and keyboard issue:
Swiftkey is typically one of the first apps I install, so can't comment on this.
Youtube:
Haven't tried the Youtube app/ site yet. I'm thinking this MAY tie into our DNS issue.
Further impressions:
stock browser isn't vanilla based, and isn't hardware accelerated, so it's a tad choppy (forcing 2D acceleration doesn't seem to work, either)
stock browser has a neat feature whereby if you swipe from the right bezel going left, it'll reveal the tabs; pretty intuitive in that regard, IMO
I tried the DNS level 3 and that didn't work.
One question did you set external sd to main storage? It doesn't seem to save apps on it?
Sent from my HUAWEI U9510E using xda app-developers app
Aw boo.
And yeah, I have external SD as main. AFAIK, that setting is only for things such as pictures/ videos, and not for apps.
Apps will always default to the internal storage, which is where the App 2 SD program comes into play.
EDIT: Hmm, I wonder if LUV's version (option C, per this thread) is any better than B. Simon, have you tried this one as well?
Hmmm weird bc without setting it my pics and video already saves on external.
Can we not just flash a stock 4.1.2 and flash the radio? I'm guessing gps and camera won't work properly? I don't like the Huawei 4.1 to be honest :s I'm back to 4.0 haha just can't stand the setting menu.
By the way I'm just curious on how you guys got this phone? Through windmobo?
Sent from my HUAWEI U9510E using xda app-developers app
Hmm, maybe the camera app itself ignores the system settings, and defaults to external SD on its own...
I don't think flashing a stock 4.1.2 would be that simple, otherwise we wouldn't need to go through these loops (via Chinese ROMs) just to obtain JB. Hence, my anxiety for a CM10 release.
I myself am pondering flashing back to stock, but the touch responsiveness of JB would be hard to let go of. Granted, it's a bit of an improvement only, but still.
Might try LUV's ROM later tonight.
And yes, I got this through Wind (on a TAB, nonetheless). I don't think this phone is available anywhere else at the moment, as far as Canada is concerned?
Sighhh I miss flashing roms I do it so much it's like I'm addicted haha. I still got my GNex to mess with.
Have anyone compiled their own rom before from free sources?
I guess we can try to learn to do that and cook up a rom for this phone that would be cool.
I'm having an issue with wify on ics I cannot connect to my school secure wifi. I had all my credential set up but it won't even attempt when I press connect.... You guys experiencing this too?
By the way have you tried the DNS to fix the market? I read somewhere that the app doesn't seem to work on jb?
Sent from my HUAWEI U9510E using xda app-developers app
I only enjoy flashing when the ROMs bring about new, practical features, performance improvements aside. I always get a chuckle out of Apple fans who jump for joy whenever an update is released. My response? "Yeah, remember how you felt when Apple released that update? Now picture that feeling, but almost every day... welcome to Android."
I'd love to get into ROM compiling, but programming is anything but my forte. I'll leave it to the Linux-heads and the guys behind Cyanogenmod, SlimBean, etc., hehe.
Odd. My wifi worked perfectly fine on the stock ROM, connecting to my home router (WPA2 Personal).
I ran across someone that said that if you attempted to use SetDNS without root, that you could possibly hose your wifi. Considering we are rooted now, I haven't the idea as to why you can't connect to the school.
SetDNS set to Google's DNS didn't work, unfortunately. Might be a glitch between the app and the ROM itself, perhaps.
(My school uses 802.1xEAP. I know I set it correctly because my GNex connects fine.) ** solved
Yes I do rmb the days when I had the iPod touch 2g and I hated how things look soo boring and function so limited so modified the crap out of it through Cydia. They had pull down menu already many years ago in Cydia and apple didn't pick it up till recently lol.
Is Huawei working on 4.1 for global firmware? I hope they keep the stock lock screen and stock menu.
Can't wait for someone to release 4.1 AOSP!
By the way compiling shouldn't be too hard? There are many tutorial and program to auto compile I rmb I had a program like that few years ago...
Sent from my HUAWEI U9510E using xda app-developers app
Per this thread, it seems that we'll be getting JB officially very soon. Bit late IMO, but better late than never.
Bit surprised about what Telco wrote about the XL's reception though, as it's quite the contrast to what Howard found with his.
Battery life
Hi I just wondering if any of you on the 4.1 can compare the battery life with me. I think I read it somewhere that the 4.1 improves battery life significantly. Here are my results
4.0.4 ICS, Screen brightness on auto. On battery save mode most of the time
By the way anyone fixed the play store/ you tube issue?
12andy said:
Per this thread, it seems that we'll be getting JB officially very soon. Bit late IMO, but better late than never.
Bit surprised about what Telco wrote about the XL's reception though, as it's quite the contrast to what Howard found with his.
Click to expand...
Click to collapse
About the reception i have to say i agreed! My GNex never looses signal completely (just down to no bar but still barely connected) but the ascend drops to no service. At school too I noticed I get drop signals in some areas that i didnt notice before. Maybe that have to do with the battery saving mode? I will try putting on performance mode to test it out in those areas.
The way you grip I do notice some drop in signal. Probably the architecture and location of the antenna
nvana said:
By the way I'm just curious on how you guys got this phone? Through windmobo?
S
Click to expand...
Click to collapse
No problem to get the phone in my country. More than 10 different shops.

[ROM][UNOFFICIAL][KitKat 4.4.4][SM-T530NU] CyanogenMod 11 [04/26/2015]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?

[ROM][SM-T580][SM-T585][UNOFFICIAL] LineageOS 14.1 | Android 7.1.2 20171231+TWRP 3.2

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Now I can recommend the firmware for daily use.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Root
Settings -> About tablet -> press 7 times "Build number"
Then Settings -> Developer options -> Root access
Work
Ril, wifi, sound, vibra, bluetooth, camera, sdcard, gps, mtp, otg, flashlight
Known Issues
Links
LineageOS Builds
SM-T580
5. 20171231: gps fix: https://drive.google.com/file/d/1OIZsMIbqeJDyo-OuL4sEJH7A5pLzaN7-/view?usp=sharing
4. 20171202: flip cover, offline charge: https://drive.google.com/file/d/1BGAPDkb3EKspHm98VFV6ULoIpKjJhJgN/view?usp=sharing
3. 20171201: flip cover, minimum autobrightness, cpu settings from original stock boot: https://drive.google.com/file/d/1StcJjaI7lMHj-DM2aql4XDr6gd2BNqSW/view?usp=sharing
2. 20171130: bluetooth, sdcard as internal storage, cleanup, overlay framework with correct values from stock: https://drive.google.com/file/d/1IzjmpVcHe1whXFYh2LXGyTz2rRams5oV/view?usp=sharing
1. 20171127: https://drive.google.com/file/d/1WI9aeY-GShwjMRZTLc5eeOz8w2TcWj_e/view?usp=sharing
SM-T585
6. 20171231: https://drive.google.com/file/d/1sPCij87eKwtsdZhU3XyDFf3GLeqKXl4w/view?usp=sharing
5. 20171202: flip cover, offline charge: https://drive.google.com/file/d/12YSZbhtaG5swob9HxkNpd5DLLWpfMbTb/view?usp=sharing
4. 20171201: flip cover, minimum autobrightness, cpu settings from original stock boot: https://drive.google.com/file/d/1vQuL1LXOk5Kow3fEjNj5r0ey8K7Doum2/view?usp=sharing
3. 20171130: bluetooth, sdcard as internal storage, cleanup, overlay framework with correct values from stock: https://drive.google.com/file/d/1s5zjiZr66ySO3DiUKxt06xWimE0KkJI6/view?usp=sharing
2. 20171125: a lot of changes (ril, camera, gps, video play, some optimizations), now firmware almost done, and can be use for daily drive. Please use my twrp, in other case you need remove first line in \META-INF\com\google\android\updater-script inside archive: https://drive.google.com/file/d/1MELQV4w1zK0VzV_-r6sHSsG8gXgSjn7_/view?usp=sharing
1. 20171116: https://drive.google.com/file/d/15uBG7WsGX9j9lO8-C3VkFjj6wfQzoMuY/view?usp=sharing
TWRP
SM-T580
Use official TWRP from: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
SM-T585
This twrp - this is official 3.1.1.0 for wifi version, I had repacked it with T585 info.
A first line in any lineage firmware - version check, in T585 it's should be gtaxllte. With this twrp it's correct.
2. 20171202: odin version 3.2.0.0 (md5: a9081075f801f9a4881f2a11365111cf): https://drive.google.com/file/d/1140aSajZTl4wcdMs8IbXLP04Yjoi2-7d/view?usp=sharing
1. 20171125: odin version 3.1.0.0 (md5: 33dfa464ef42e7d408e9d1639b2aa137): https://drive.google.com/file/d/17yNKuK4lzpInzkvy0ve8iGL2NBkydl0Z/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Variant: any, usually I'm using micro or nano
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
SM-T580
Device: https://github.com/Valera1978/android_device_samsung_gtaxlwifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi
SM-T585
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Congrats with beginning!:good:
Wait for fix calls and mobile data.
Congrats Brother ????
Good work.
This T585 build also booted on T580. Works fine, only RIL staff is annoying (T580 do not have SIM)
I built my own T580 LOS 14.1 build. It booted but media and audio are dead.
tank0412 said:
Good work.
This T585 build also booted on T580. Works fine, only RIL staff is annoying (T580 do not have SIM)
I built my own T580 LOS 14.1 build. It booted but com.android.phone is crashed. Discovering it now.
Click to expand...
Click to collapse
if u dont hav sim on it than remove that apk issue will be fixed autmoatically
Just flashed this on a t580 and all seems well other than the known bugs thank you so much for the build hopefully many more to follow
I've been following your work on this device since you started. Very excited to give it a try. Thank you so much for all of your efforts.
Can we get some screenshots????
paulo boë said:
Can we get some screenshots????
Click to expand...
Click to collapse
Screenshots have no differences from other devices with LOS 14.1
YEESSS! Congrats buddy! Keep going!!!! I will try this asap!
Sad about no mobile data. Can't live without that. Sorry. Big hopes. I'll wait until it works and I'll give it a try.
Thanks for your effort.
Enviado desde mi SM-T585 mediante Tapatalk
tank0412 said:
Good work.
This T585 build also booted on T580. Works fine, only RIL staff is annoying (T580 do not have SIM)
I built my own T580 LOS 14.1 build. It booted but com.android.phone is crashed. Discovering it now.
Click to expand...
Click to collapse
Nice to see you cover this development as well. Maybe it is possible to join forces with Valera1978 ? I will try this build as well of course and report on issues. Hopefully it is not too much of a problem to run it on a T580 (without SIM).
@Valera1978. Your ROM performs very well (it is fast too !).
As expected, it runs well on a SM-T580 as well, you can just skip the SIM part in set-up with no problem at all.
Of course it is still work in progress, so bugs to be expected. However I concluded that sound is working properly ,which is fantastic.
In your opening post you said GPS is not working, but I think it is working (Navmii and Google maps anyway).
I did not find many problems, but I can report some:
- It is a bit strange that in setup you are being asked to put back a backup from the cloud while you have not been able (yet) to set up your internet connection). However this provlem can be circumvented easily by just answering that you want to set-up as a new device. In the next screen you set-up your internet connection and then you go can go back and choose to restore from backup (which works flawlessly);
- External SD card cannot be formatted as "internal storage", which is a pity, because I use a brand new 128 Gb SD card (this works in the stock ROM, so I think it is some kind of a bug);
- On an SM-t580 there is of course no SIM. In the lock screen I now see "no service". On a post to Tank0412 Oves786 suggests to remove an APK, but I wouldn't know which one it is (otherwise I would try, although I realize that other things should be removed as well, like the dialer program). The functioning of the tablet is not impaired in any way by this (as far as I can see);
- Gboard (an app from Google) apparently is not functioning properly: swiping does not work at all, although it is supposed to do so. In the standard AOSP keyboard however swiping is no problem.
I'm waiting for the Bluetooth to work in order to flash this Rom!!
JoostA said:
Nice to see you cover this development as well. Maybe it is possible to join forces with Valera1978 ? I will try this build as well of course and report on issues. Hopefully it is not too much of a problem to run it on a T580 (without SIM).
Click to expand...
Click to collapse
I also have the T580. But this is my wife's tablet, and I can not take it up for a week for develop. But as soon as there is a stable version for the T585, I'll take it for a short time (1-2 days) and fix it too.
JoostA said:
@Valera1978. Your ROM performs very well (it is fast too !).
As expected, it runs well on a SM-T580 as well, you can just skip the SIM pat in set-up with no problem at all.
Of course it is still work in progress, so bugs to be expected. However I concluded that sound is working properly ,which is fantastic.
In your opening post you said GPS is not working, but I think it is working (Navmii and Google maps anyway).
I did not find many problems, but I can report some:
- It is a bit strange that in setup you are being asked to put back a backup from the cloud while you have not been able (yet) to set up your internet connection). However this provlem can be circumvented easily by just answering that you want to set-up as a new device. In the next screen you set-up your internet connection and then you go can go back and choose to restore from backup (which works flawlessly);
- External SD card cannot be formatted as "internal storage", which is a pity, because I use a brand new 128 Gb SD card (this works in the stock ROM, so I think it is some kind of a bug);
- On an SM-t580 there is of course no SIM. In the lock screen I now see "no service". On a post to Tank0412 Oves786 suggests to remove an APK, but I wouldn't know which one it is (otherwise I would try, although I realize that other things should be removed as well, like the dialer program). The functioning of the tablet is not impaired in any way by this (as far as I can see);
- Gboard (an app from Google) apparently is not functioning properly: swiping does not work at all, although it is supposed to do so. In the standard AOSP keyboard however swiping is no problem.
Click to expand...
Click to collapse
"In your opening post you said GPS is not working" - on T580 - this is another key in kernel. On T585 - i'm working with it. Yesterday I had find reason - if I'm manually (via adb) running modem - I see baseband, imei, and gps starting work too. At least now I known - problem in ramdisk, vendor and device config is correct for ril.
"back a backup from the cloud" - this is gapps bug, as I remember wizard ask about backup before you enter your google account.
"External SD card" - strange, will check, T580-585 should be same logic.
"On an SM-T580 there is of course no SIM" - not enough remove apps, need build firmware without telephony. Because settings also included changes in framework.
"Gboard (an app from Google) apparently " - will check, but later, primary problems is first.
Jamess27 said:
I'm waiting for the Bluetooth to work in order to flash this Rom!!
Click to expand...
Click to collapse
I'll check after ril, but I'm on 90% sure - it's the same problem.
Thank you for this, for an Alpha its very good. Its installed now on my T580 . The kernel is Permissive and can't be switched to Enforcing, is this something we could have in a future release, a kernel with the ability to change?
Amazing work, congratulations for bringing this to us, its a game changer for the T585/580. When I look at my Ti Back-up for any missing apps and see all that Samsung bloat-ware and Knox related stuff...well how good to see them gone
btb55 said:
Thank you for this, for an Alpha its very good. Its installed now on my T580 . The kernel is Permissive and can't be switched to Enforcing, is this something we could have in a future release, a kernel with the ability to change?
Amazing work, congratulations for bringing this to us, its a game changer for the T585/580. When I look at my Ti Back-up for any missing apps and see all that Samsung bloat-ware and Knox related stuff...well how good to see them gone
Click to expand...
Click to collapse
basically its not an issue now
first let him fix all bugs left or just make it stable with fixing ril and other network stuffs
Format SD card as Internal memory
@Valera1978. Maybe just nonsense what I discovered but maybe it is not, so I think I should share this.
I discovered Samsung S7/S7 edge suffer from the same problem that it is not possible to format their SD card as internal (which however is possible in the original Samsung sofware for the SM-T580/ 585 as I mentioned earlier).
So I thought it would be a nice experiment to try the solution I found in:
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
After having read that, what I did was no more then simply issuing the commands:
adb shell
sm list-disks
This returned:
"CANNOT LINK EXECUTABLE "app_process": "/sbin/libcutils.so" is 64-bit instead of 32-bit
Aborted"
I now suspect - without really knowing why or how - that maybe a 64 bit module (or maybe the reverse: some 32 bit module) is interfering some way with the formatting of the disk as internal.
This is not the biggest of problems of course, this build already performs really nice and smooth anyway. However of course I do hope it proves to be is a lead to the solution.

[Magisk ROM][RMX2001][90HZ][Debloat]PpPmod[v1.1]

PpPmod for Realme UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About PpPmod
PpPmod is a port of the excellent xXx NoLimits magisk ROM for Oxygen OS. It's a systemless modification to the default Realme UI that allows the user to get much more out of his device than the default configuration allows.
But why a magisk ROM?
For two reasons:
1. Realme devices offer good price to performance ratio, but in many cases they lack a developer community around them to build those ROMs the users want.
2. Realme UI is not that bad honestly. It offers good performance, it's not too crazy aesthetically and its bloatware isn't baked deep into the system.
It's also a much safer way to modify Mediatek devices. As long as you've managed to root your phone, you are good to go. If something goes wrong, just wipe data and no harm, no foul.
Supported devices
While in theory, any Realme device with Realme UI v1, Android 10 and a full HD screen resolution should be compatible, the only two devices this has been tested on are a Realme 6 and a Realme 6 Pro. For the curious, i own the later.
Ok, but what does it do?
- Port of xXx NoLimits for Oxygen OS
- Fully systemless Realme UI ROM mod for magisk
- Designed to work with all phones that run RealmeUI v1, Android 10 on full HD screens, including MTK ones
- Fully configurable installation, every component is optional
- Includes comprehensive debloating options
- Optional build.prop tweaks
- Many kernel tweaks that can be adjusted and combined, in order to target different degrees of performance and battery life
- 90hz/120hz for ALL apps when the display is set to its high refresh rate
- GMS Doze included
- Ability to disable analytics
- Ability to disable wakelocks
- Can enable full screen gestures (swipe up) for 3rd party launchers
- Ability to set custom bootanimations from a built in list, or as a user selected bootanimation.zip
- Includes extra launchers, sounds and icons from popular device brands like Pixel and OnePlus
- Gcams for both Qualcomm and Mediatek devices are included (by Urnyx and onFire)
- Youtube Vanced, detached from the playstore so no pesky updates can override it
- Google Dialer and Contacts, both old and new versions
- Custom density modes
- Ability to systemize apps
In order to set your own bootanimation, place a bootanimation.zip inside /sdcard/PpPmod. You can also place a shutdown/restart animation named rbootanimation.zip there. Make sure that your bootanimations are 1080 pixels in width, or they won't work as you'd expect. If you set option CustomBootAnimation to 1 in PpP.profile, your animations will be used during start up and/or reboot, instead of the default ones. For more information about the PpPmod folder and the PpP.profile file go to Installation Instructions.
If you want to systemize an app for whatever reason, just place the apk inside /sdcard/PpPmod/apps., before flashing.
Concerning debloating there is a master switch you should toggle if you want your individual options to work. Set IndividualDebloatSelection to 1.
Installation Instructions
You will find detailed installation instructions along with download links on post #3
Screenshots
For screenshots, press here
Thanks to:
xXx
ahmed_radaideh
dustintinsley
gloeyisk
k1ks
andip71
linuxct
Mostafa Wael
mrRobinson
osm0sis
rufus.wilson
snowwolf725
topjohnwu
Zackptg5
ZaneZam
Kevin Saiza
Tytydraco​
XDA:DevDB Information
PpPmod, ROM for the Realme 6
Contributors
FatherJony
ROM OS Version: Android 10
ROM Firmware Required: RealmeUI
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-09-14
Created 2020-09-03
Last Updated 2020-09-14
Changelog
Version 1.1
Fixed a bug where enabling HighRefreshRate had no effect on the first boot after installation.
Updated Google Dialer to the latest version.
Updated sqlite to the latest version.
Reworked kernel tweaks, with some inspiration from Ktweak by tytydraco.
New ReadAhead option added. This allows the user to disable, or set the readahead cache to a percentage of the device's memory. Default is 1 (cache disabled).
New CPUGovernorTweaks option added. When this is enabled, schedutil and interactive governor tunables are tweaked in order to increase performance. The default governor will also switch to schedutil or interactive depending on availability. Default is 1 (enabled).
Reworked CPUInputBoost option to make it more granular. You can now select from small, medium, high and max presets. For more info about them read the profile description.
Reworked CPUStuneBoost option to make it more granular. You can now select from small, medium, high and extreme presets. For more info about them read the profile description.
Installation
PpPmod allows for a fully customizable installation. The way this works is via a configuration file called PpP.profile. You will always be able to find the latest version of this file on this post. Make sure you edit this file on Notepad++ if you are opening it on Windows in order to preserve the Unix EOL format.
Requirements:
Realme UI v1 on Android 10 and display width of 1080 pixels
A working Magisk installation of v20.4 or higher
PpPmod should only be flashed via Magisk Manager
First time installation:
Place PpP.profile in /sdcard/PpPmod/ and edit it to personalize the installation to your liking
Flash the PpPmod zip via Magisk Manager
Reboot. Wait for at least a minute to let all installation options take effect.
Done
The first time you install, chances are that the PpPmod folder will not be in /sdcard, so you have to create it yourself. If you don't place PpP.profile there, the mod will be installed with the default options when you flash it and place the default PpP.profile inside /sdcard/PpPmod/.
Update to a newer version:
Open Magisk Manager and uninstall the previous version
Reboot
Wait for a couple of minutes after reboot as the uninstallation process can take some time
Install the newer version via Magisk Manager. Don't worry about changes to PpP.profile, they will be merged to your older version profile
Reboot. Wait for at least a minute to let all installation options take effect
Done
Uninstallation:
Press the waste bin icon next to the mod's name on the Magisk Manager
Reboot. Wait for a couple of minutes after reboot as the uninstallation process can take some time
Done
Downloads:
PpPmod v1.1
PpP.profile v2
PpPmod v1.0
PpP.profile v1
FAQ
Q: I just installed PpPmod and my phone has heated up and stutters, is this normal?
A: Yes, the installation process is fairly intense, and during the first boot following the installation, a lot of stuff happens in the background. Just let your phone settle for 10 minutes and it should be fine.
Q: I did all that and my phone still heats up, you liar!
A: Well, check your settings. PpPmod offers many options for tweaking, but not every one of them is suitable for all phones, or all usage patterns. In general, the higher performance settings may be fine for general usage and offer you a flagship like experience along with a high refresh rate, but will cause excessive heat and throttling during gaming.
For example, maybe a 12nm chipset shouldn't be pushed aggressively by enabling CPU boost options, especially if you game alot. You may gain a brief performance boost that will sooner or later be the cause of intense overheating, which will cause throttling, which will cause stutters. In short, try to be reasonable with your settings and expectations, PpPmod will not magically turn your mid range chipset into an SD865.
PpPmod is also not designed to work along with other magisk mods that adjust performance by altering kernel behavior. If you want to use such mods with it, try disabling every PpPmod performance setting, like:
KernelTweaks
LMK_RAM_Management
ReadAhead
DisablePeWq
DisableHotplugging
IncreaseMinGPUFreq
CPUGovernorTweaks
CPUStuneBoost
CPUInputBoost
The result may still not be ideal, but this is your best bet.
Q: My debloating options aren't working!
A: You forgot to set option IndividualDebloatSelection to 1.
Q: I think i found a bug, what is the best way to report it?
A: You should always include a detailed description of what triggers the bug, its effects, your specific phone model (including hardware characteristics like RAM and storage), firmware version, your PpP.profile and preferably a logcat from when the bug occurred.
Q: Can i be a beta tester? I swear i am awesome!
A: As long as you meet certain conditions, sure! The conditions are:
First and foremost, you must understand that beta testing doesn't mean early access. Most of the time you will have to do things that may be inconvenience you, or lead to loss of time and data (factory resets)
You should know at the very least how to setup and use adb
You should have A realme device with Android 10 and Realme UI v1
Q: Can i ask for a feature?
A: Sure, but keep in mind that PpPmod isn't primarily geared towards a specific device. So while device specific features are not out of the question, priority will be given to features that affect a range of devices.
Q: My phone isn't listed in supported devices, but it's a Realme device with Realme UI v1, Android 10 and a full HD resolution, should i give this a try?
A: Yes, as long as you don't mind resetting your data if something goes wrong, you should. That's exactly what i am trying to achieve with this mod. Normally, a new phone like for example the Realme X7 Pro would not have any options for customization on release, and may never get much due to the Mediatek soc. But PpPmod should work immediately, at least in theory. Even if there are some device specific issues i will do my best to fix them, and in the worst case scenario the phone is still safe from any permanent harm. Just reboot to recovery and reset data.
Q: PpPmod sucks and i wanna uninstall it. Must i also remove magisk?
A: NO, you don't have to and in fact you shouldn't if you don't have a reason unrelated to PpPmod, as magisk resides in your boot partition and thus unlike PpPmod, can mess with your device if you aren't careful.
Q: What does PpP mean?
A: No one knows fo sure. Some thik that it means Pro Plus Prime. Some other, less charitable persons claim it means PapaPowah instead. We may never know the truth.
Q: What do you plan for your next project?
A: Rewriting Android in Objective Cobol
Q: Is it true that you are actually a boomer?
A: Ok, that's enough. You guys have crossed the line and now i am forced to conclude this QA session.
FatherJony said:
Reserve
Click to expand...
Click to collapse
Good job dude
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
PapaSid26.12 said:
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
Click to expand...
Click to collapse
Yes, it works. But the whole point of a systemless mod is that you CAN'T brick your phone. Worst case you will just have to wipe data via recovery.
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
marvinvvh said:
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
Click to expand...
Click to collapse
I am sorry to hear that about the EU version. I thought that this would have been resolved by now. Unfortunately this is a magisk mod, thus it doesn't work without magisk.
Even after making changes in PpP.profile I'm getting default settings
Shanpatil said:
Even after making changes in PpP.profile I'm getting default settings
Click to expand...
Click to collapse
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
FatherJony said:
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
Click to expand...
Click to collapse
Can u give some SS??
I bricked my phone...
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
fraillesgeon said:
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
Click to expand...
Click to collapse
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
FatherJony said:
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
Click to expand...
Click to collapse
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
fraillesgeon said:
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
Click to expand...
Click to collapse
I did the same mistak. Howevre here is a solution.
If you have sd card, download latest ozip file from realme wessbite and place in root of sd card. Then insert it into your realme 6 and boot into recovery using power and vol down. After that install zip from total storage and install from sd card. Hopefullt it will be back.
On an another note there shall be some key combo for booting into fastboot mode
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
I'm back!
FatherJony said:
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
Click to expand...
Click to collapse
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Can you do the step by step process on how to flash it using magisk?
fraillesgeon said:
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Click to expand...
Click to collapse
Great news! I am really glad you were able to save your phone. As a rule, only use internal storage (/sdcard) for important operations.
I am looking forward to your impressions!

[ROM][9.0][N5100/N5110/N5120][UNOFFICIAL] /e/

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my first versions for the Samsung Galaxy Note 8.0 on /e/.
I'm actually in the middle of making it official, but at first I have to solve some remaining problems.
For all people, who doesnt know what /e/ should be,
just take a look here:
/e/ (operating system) - Wikipedia
en.wikipedia.org
e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data
your data is YOUR data
e.foundation
Here you can see how far everything is working:
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
USB
Video playback (HW/SW)
RIL
GPS, 3D fix doesn't work, but navigation seems to work fine in my case.
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Spoiler: Whats not working
Bliss launcher won't rotate your screen, so I've included trebuchet from lineageos, only for testing
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: Changelog
06.04.2021
10.04.2021
13.04.2021
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][9.x][N5100/N5110/N5120][STABLE] /e/, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS, /e/
Version Information
Status: Alpha, built on LOS16.0
Release Date: 2021-03-30
Created 2021-03-30
Last Updated 2021-04-13
*Reserved
I have not been able to download the file n5110 the download is interrupted in a certain time, I thought it was my internet service and I tried to download from my cell phone with my data plan and the same thing happens.
Conmauro24 said:
I have not been able to download the file n5110 the download is interrupted in a certain time, I thought it was my internet service and I tried to download from my cell phone with my data plan and the same thing happens.
Click to expand...
Click to collapse
Hi,
I'm facing the same problem when I try to download, I will upload it to AFH later,
somehow the xda server seems to have a problem.
html6405 said:
Hi,
I'm facing the same problem when I try to download, I will upload it to AFH later,
somehow the xda server seems to have a problem.
Click to expand...
Click to collapse
Thank you very much, I really want to test your rom, it is fascinating to see how this tablet works in an incredible way thanks to its development.
Also looking forward to this very much!!
Thank you for all your hard work!
Links are online!
I honestly can't stop getting excited about this tablet, with this system it works super well, it's more fluid, consumes less battery and it looks beautiful. I share some screenshots of what this looks like after customizing it. I will not tire of thanking the developer who continues to give us happiness with these rom's
Also played shortly with this new /e/ rom. Very smooth and fluent, wonderfull! Enjoying this googlefree experience very much! Going to stay on it and not going back to LOS unless i have to.
Haven't had lot of time to test all functions but here is how it worked for me:
- wifi works flawlesly.
- screen rotate works well on trebuchet, haven't tried with the other native launcher.
- haven't tested BT, call and message functions or mobile data. will do that later.
- camera app opens, but i get message that the picture can't be saved. Same for both cameras and video. Seemed to have something to do with the ability to write on the intern scdard. I tried to change the folder for saving pictures in but it didn't work.
- it wasn't possible to install apps from the /e/ App Store. THe app itself most often crashed when i tried that. And there seemed to be a small symbol of a locked padlock next to all the apps on all the app lists. Suspecting that installing might require logging in the user account, is that so? Which was a bit strange in that case, and seems to be necessary for several other apps, like notes, calender, and such. Installing from fdroid worked with no problem.
- I missed the possibility to shut down those apps i don't need so they no longer show in the app drawer.
But overall awesome ROM from the awesome dev. Can't thank you enough and looking forward to your further developing!
Had a chance to play a little with the more functions:
-Mobile data works.
- Calls work.
- Messages work. haven't been able to test MMS.
- BT is a complete no-go. Tried to connect with both a small speaker and a keyboard, and despite trying for almost half hour, it didn't work. N5120 finds those gadgets nearby, but it can't connect.
- Camera still doesn't work. Can't save the pictures on internal storage.
- Trying to open Gallery-app will get you a message that no external storage is available. Even if it is.
- Tried to set up an external sd card as extra storage but formatting didn't work.
- The Files-app cannot show internal storage either.
- App store doesn't allow installs.
- Recorder-app annoyingly buggy. Gets stuck in recording sound mode when started. Recording video produces a video that can't be opened. VLC app is blocked from viewing it by the native app.
- The tablet just frose. Had to hard close.
prkfsz said:
- screen rotate works well on trebuchet, haven't tried with the other native launcher.
Click to expand...
Click to collapse
Thanks for your report, screen rotation isn't supported on the original /e/ Blisslauncher, so
I decided to include the Trebuchet for this unofficial version.
prkfsz said:
- camera app opens, but i get message that the picture can't be saved. Same for both cameras and video. Seemed to have something to do with the ability to write on the intern scdard. I tried to change the folder for saving pictures in but it didn't work.
Click to expand...
Click to collapse
In my case, it was exactly the same behaviour at the first start, after closing the camera completely and reopen it, it's working.
I've recognized that there's sometimes a problem when you try to record with the front cam.
(I guess it is fixed when you set the fps to 30)
With gCam on LOS 16 it's working fine.
prkfsz said:
- it wasn't possible to install apps from the /e/ App Store. THe app itself most often crashed when i tried that. And there seemed to be a small symbol of a locked padlock next to all the apps on all the app lists. Suspecting that installing might require logging in the user account, is that so?
Click to expand...
Click to collapse
Hmm good question, I will take a look at it.
I'm pretty sure, that the /e/ App Store need's many improvements,
but we have to wait for them.
prkfsz said:
- I missed the possibility to shut down those apps i don't need so they no longer show in the app drawer.
Click to expand...
Click to collapse
prkfsz said:
- BT is a complete no-go. Tried to connect with both a small speaker and a keyboard, and despite trying for almost half hour, it didn't work. N5120 finds those gadgets nearby, but it can't connect.
Click to expand...
Click to collapse
Thanks, this could be to selinux related, I will debug this as soon as I can.
prkfsz said:
- Trying to open Gallery-app will get you a message that no external storage is available. Even if it is.
Click to expand...
Click to collapse
Hmm this is strange, is your storage accesable at all? Is any file browser able to access your storage?
Maybe you have to format data /media in TWRP.
prkfsz said:
- App store doesn't allow installs.
Click to expand...
Click to collapse
This also point's to a not accessable storage...
prkfsz said:
- Recorder-app annoyingly buggy. Gets stuck in recording sound mode when started. Recording video produces a video that can't be opened. VLC app is blocked from viewing it by the native app.
- The tablet just frose. Had to hard close.
Click to expand...
Click to collapse
Same...
AL-RajheBank said:
Alrajhebank.sms
Click to expand...
Click to collapse
?
html6405 said:
Thanks for your report, screen rotation isn't supported on the original /e/ Blisslauncher, so
I decided to include the Trebuchet for this unofficial version.
In my case, it was exactly the same behaviour at the first start, after closing the camera completely and reopen it, it's working.
I've recognized that there's sometimes a problem when you try to record with the front cam.
(I guess it is fixed when you set the fps to 30)
With gCam on LOS 16 it's working fine.
Hmm good question, I will take a look at it.
I'm pretty sure, that the /e/ App Store need's many improvements,
but we have to wait for them.
Thanks, this could be to selinux related, I will debug this as soon as I can.
Hmm this is strange, is your storage accesable at all? Is any file browser able to access your storage?
Maybe you have to format data /media in TWRP.
This also point's to a not accessable storage...
Same...
Click to expand...
Click to collapse
I tried closing and restarting the camera many times. Nothing.
DOn't know about the accessible storage, as i said, it could install apps from the microsd card, like fdroid. And update it.
The external storage (microsd card) is accessible in the native explorer (files-app). Tried to format it too, not sure about the results, it ran it till the end and said it was done, but still couldn't see it. First when i formatted it in another device it saw the extern sd card. So, the native explorer sees the microsd card, but not the internal storage.
Hello
html6405 said:
Hmm good question, I will take a look at it.
I'm pretty sure, that the /e/ App Store need's many improvements,
but we have to wait for them.
Click to expand...
Click to collapse
First of all, kudos = I'm testing your /e/ ROM with a damaged N5100 (main camera KO & unreliable SIM slot) and it's behaving quite well.
Found similar issues with App Store (internal failure errors), but I've managed to bypass most of them after Disable/Enable Auth Storage & reboot.
The only error still there was during the installation from App Store of System App / MicroG with Support for Exposure Notifications. However, it was only a matter of package signature mismatch = enabling root for ADB & manually replacing the GmsCore APK in priv-app, everything worked back again.
About Bluetooth, I haven't tested it yet for BT pairing (doing it tomorrow), but for instance BLE Advertising of GAEN Contact Tracing Apps seems working fine.
html6405 said:
Same...
Click to expand...
Click to collapse
When you perform the first screenrecording, it doesn't create the subfolder Screenrecords into the Movies folder. Therefore, even if it says that the movie has been saved, there is nothing to retrieve.
I've solved it by deleting such 1st screenrecord from the recorder app, then disable/enable Storage Auth & reboot. After the reboot the screenrecord subfolder was there & I've managed to perform new screen records without issues.
What version of gcam works for you? I am using gcam go mod but the image remains static, activate the HAL3 to see if it could start well and nothing.
prkfsz said:
I tried closing and restarting the camera many times. Nothing.
DOn't know about the accessible storage, as i said, it could install apps from the microsd card, like fdroid. And update it.
The external storage (microsd card) is accessible in the native explorer (files-app). Tried to format it too, not sure about the results, it ran it till the end and said it was done, but still couldn't see it. First when i formatted it in another device it saw the extern sd card. So, the native explorer sees the microsd card, but not the internal storage.
Click to expand...
Click to collapse
How did you install the rom, with a complete data wipe? Or did you just wiped data without data/media (factory reset?)
If you have backuped your files, you could try to reboot into TWRP and choose Wipe->Advanced Wipe->Internal Storage and reboot.
RawMain said:
Found similar issues with App Store (internal failure errors), but I've managed to bypass most of them after Disable/Enable Auth Storage & reboot.
Click to expand...
Click to collapse
I don't know why yet, but some apps doesn't get storage access at first start, they just need to be closed (also in the background) and restarted, then they should work.
Conmauro24 said:
What version of gcam works for you? I am using gcam go mod but the image remains static, activate the HAL3 to see if it could start well and nothing.
Click to expand...
Click to collapse
The version I'm using in my LOS 16, ( I don't know the exact version number yet, I can't look ),
but I will try to fix this problem with /e/'s open camera.
html6405 said:
How did you install the rom, with a complete data wipe? Or did you just wiped data without data/media (factory reset?)
Click to expand...
Click to collapse
I usually cleanflash but this time i was unsure. So i installed again, after wiping everything. And get exactly the same behavior from the device.
Hmm strange, I don't understand why, on my device's it is working fine, it makes no difference if I just do a factory reset or if I wipe /data completely .
Maybe you could send me a logcat or a complete syslog file?
Then I will try to find out whats wrong.
I would if i knew how..
You could use the syslog app and create a complete log file after a reboot, or adb shell .
adb shell
su
logcat > /sdcard/logcat.txt

Categories

Resources