Disclaimer
I'm am not responsible for bricked devices, flashing custom ROM's/Recovery's is done so at YOUR OWN RISK!
Information
This is a standard Lineage build without any extras & compiled with stock SU6 6.0.1 kernel
Download
http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Installation
I recommend doing a full wipe before flashing!
Flash ROM using TWRP
Flash GAPPS 6.0 arm package of your choice
Reboot & wait for Android to boot
Version Information
Status Beta
ROM OS 6.0.1 Marshmallow
ROM Kernel 3.10.49
Created 2017-08-24
Updated 2017-10-07
Thanks goes out to @wbrambley for his involvement in testing & helping to solve / fix bugs!
I noticed that "mm-pp-daemon" was stopping the CPU from going in to sleep state and keeping it at full clocks but after killing the process it reloaded and was fine.
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
wbrambley said:
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
Click to expand...
Click to collapse
I have merged the commit you made to github & can confirm NFC now enables for me.
Update has been uploaded http://www.mediafire.com/file/7bjnwaaupm4ejf0/lineage-13.0-20170903-UNOFFICIAL-p839v55.zip, first post link also updated.
Camera now working & NFC now enables thanks to @wbrambley
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
coolbook1 said:
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
Click to expand...
Click to collapse
Use recovery to flash a 5.1 stock ROM, then you can get temporary root. I'm guessing you've found a guide for this. After that I recommend flashing stock MM from TWRP. There's one with edited uodater-script around that will work.
Hint: look at the forum I posted earlier.
Sent from my HUAWEI GRA-L09
Thanks for your rom
I Wonder when will sensors be fixed?
Update uploaded http://www.mediafire.com/file/v5m8keoadkwkaz2/lineage-13.0-20170906-UNOFFICIAL-p839v55.zip
Sensors now working properly, also improved boot up time.
Waiting For Your Stable Version
Sensors now working properly, also improved boot up time.[/QUOTE]
thanks Nutsda I'm Waiting For Your Stable Version...
lineage-13.0-20170906
Auto rotate screen is broken in this build.
thanks
When will we see an update of your work? Keep it up.
Okay here is an updated build http://www.mediafire.com/file/wedlnkhzk4e5o81/lineage-13.0-20170925-UNOFFICIAL-p839v55.zip, playstore should now work properly & improvements to sensors (but probably still require more work).
Thank you. Market now works. Still can't install nova but overall very good. Looking forward for the first stable release
New update uploaded http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Improved audio volume,
All sensors now working - thanks to @wbrambley,
Lineage updated to 6.0.1_r80.
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
DR.iTACHi said:
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
Click to expand...
Click to collapse
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
nutsda said:
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
Click to expand...
Click to collapse
i tried your cm 12.1
that built specially for this phone laggy as hell too!
is this rom is laggy too?
i flashed your rom it's stable and not laggy like others but how to root it?
DR.iTACHi said:
i flashed your rom it's stable and not laggy like others but how to root it?
Click to expand...
Click to collapse
You have to download SuperSU to get root access as Lineage doesn't have root access built in.
Related
As was my plan all along, kltevzw official support for AOSP roms is picking up. Please see this thread for official downloads and support:
http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
My builds will cease.
-- Begin copy-pasta template from my CM13.0 build thread... please let me know if I miss updating something --
Note: I don't run this ROM personally, I really just built it. It shouldn't, but it may eat your cat.
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your
phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: When/how often are these built?
A: Less often than my CM13.0 build, but at least every week. Unlike my CM13.0 build, I don't use this ROM so I won't be doing a "does it boot" check before uploading. Please tell the entire thread if one day's build doesn't work properly.
Q: Can I get help with something?
A: I have a full-time job and travel a lot. I'll try to jump in and answer some questions, but there is a lot of info out there for you to learn on your own. Aside from you having a vzw-variant, most of the details are standard KLTE. Please see the normal Resurrection Remix KLTE thread for standard ROM help.
Click to expand...
Click to collapse
Recovery:
The standard KLTE TWRP 3.1.0-0 should mostly work, but MTP doesn't work for any klte* variant using it.
I prefer KToonsez's 2.8.6-based Recovery. It's older, but MTP works.
There are Unofficial 3.*.0-* recoveries available by @jcadduono. I find that these don't support decryption properly, which I find to be mandatory.
Like many other devices, the .zip files can be flashed in a recovery. The .tar.md5 files can be flashed in ODIN. The .img files can be flashed using Flashify, a TWRP recovery. You can even get an .img file from a .zip or .tar.md5 if you just open it up.
If you use adopted storage then things get odd. The latest recovery by @jcadduono MAY support adopted storage if you don't encrypt userdata (I personally know that TWRP handles adopted storage for jflte and d2), but I do use encryption so I don't use that recovery. It may be that you only see /data/media/0 -- if so, I find that using Flashify for each nightly is the most straightforward way to update, but you could always manually copy to /data/media/0 before rebooting to recovery. This is a standard Marshmallow and TWRP thing.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. Please note that some have reported that you cannot flash these after the aboot unlock; If you cannot flash the PB1 modem/non-hlos it shouldn't cause any big problems.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
Resurrection Remix recommends SlimGapps or OpenGapps. See their thread for discussion of pros/cons and what those users tend to use. If you use OpenGapps, make sure to use an 6.0 version for ARM architecture.
OpenGapps
SlimGapps
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
I'll build at least once per week, at least until the RR team picks up the torch. Once the build is complete, I upload it to my AFH account.
ResurrectionRemix-M v5.6.X KLTEVZW weekly-ish
Click to expand...
Click to collapse
Does/Doesn't Work:
Everyone that gives it a shot needs to let the thread know. See the Unified Resurrection Remix thread for discussion of what generally does/doesn't work with the ROM.
forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
Click to expand...
Click to collapse
Thanks:
Everyone on the Resurrection Remix and CM teams. This is 99% of their stuff with just a couple tweaks to make it build, (hopefully) boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r22 (prior to 20160406 build)
Android Version: 6.0.1_r24 (20160406-present build)
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
In order of importance:
Resurrection Remix github: https://github.com/ResurrectionRemix
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
tbclandot said:
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
Click to expand...
Click to collapse
Someone needs to be the guinea pig. I know how much a pain it can be setting a ROM up from a clean install, but if CM feels just a bit too vanilla then I'd say jump into the pool.
Alright going to download and flash it now and I will report back to you thanks for your hard work!
---------- Post added at 01:06 AM ---------- Previous post was at 12:35 AM ----------
Hagg flashed the rom and everything seems to be working so far I can make calls and receive texts I prefer RR to CM13 for the features! Just wish there was a way to get my Gear S to connect to non Touchwiz roms but oh well I'll just use it as a regular watch or maybe get an AW watch lol
Running CM13, what's different?
Hmmm extra features to be honest I like CM13 but it's so boring and as a guy that actually likes Touchwiz RR is nice because of the added customization!
So I've for RR installed. Few things I noticed right away: Built in ad-away, nice! Uses super-su. I personally have no issue with the built in root, but whatever. Other than that, it's very close to CM13 in terms of speed and look/feel.
Edit: One weird glitch I've run into on both this and CM13 is that the camera app gives and error "gallery has stopped working" when launched from the icon. If i used the double power button though, then the icon starts working. Any ideas?
Edit2 : It seems to be the default camera icon that is on the home screen in both ROMS. I noticed the graphic is slightly different from the dock as it is in the app window. Deleted bad icon and replaced with app windows one and it works fine. Probably an easy fix!
No glitches, no forced closes. Everything works, and works smooth. Very nice. My new daily driver.
Unlocked and loaded RR with OpenGApps..
No issues...running great!!
Thanks!!
Will try later, thanks haggertk for your work...
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
drewcu said:
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
Click to expand...
Click to collapse
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
tbclandot said:
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
Click to expand...
Click to collapse
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
drewcu said:
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
Click to expand...
Click to collapse
No idea on the speaker as I don't mess with it usually use headphones and I don't really use T backup but I don't see why you should have problems but you'll probably want to clean wipe when installing
drewcu
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
Not that i notice
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
6.01
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
Work great
4) Does Xposed work?
Yes
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
I advice to flash PB1 firmware no botloader
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
Yes, system, data, cache and dalvik, but dont restore system apps nor system settings
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
Dont know
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
At this time not yet
Every time I attempt to download, it fails after 55kb.....
amaury48 said:
Every time I attempt to download, it fails after 55kb.....
Click to expand...
Click to collapse
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
haggertk said:
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
Click to expand...
Click to collapse
Finally got it by switching browsers.....
Would one of you on RR be so kind as to send me the mixer_paths.xml (if that's what it's still called in MM) in your System > Etc folder (assuming folder structure is the same in MM also)? I would like to compare it to the surround sound modded file I installed in KK as per the following link: http://www.naldotech.com/enable-stereo-surround-sound-speakers-galaxy-s5. I am probably not technically capable of making the same thing possible in MM with the S5 front speaker, but it's entirely possible the same modded file I have will work in MM and it's possible a comparison will reveal only a few lines of code to modify that I could do.
Thanks in advance!
Use this thread for questions, help and anything else about LineageOS that does not belong to the ROM development itself, thank you.
FAQs
Does LineageOS support VoLTE? YES
If I install LineageOS will I lose MotoActions? We have our own implementation of MotoActions configurable under Settings -> Gestures, so the answer is No
Your ROM is unrooted, can I install SuperSU? We discourage SuperSU usage, flash our su package (arm) and then enable root access from Settings -> Developer options.
Hi @Alberto97, thanks a lot for your precious work for osprey. Just wanted to know whether dual sim is properly implemented in lineage OS? As posted by some users dual sim especially data switch is broken.
samir.saurav said:
Hi @Alberto97, thanks a lot for your precious work for osprey. Just wanted to know whether dual sim is properly implemented in lineage OS? As posted by some users dual sim especially data switch is broken.
Click to expand...
Click to collapse
Data switch is not broken, simply when switching from wifi to mobile data sometimes you need a reboot to make mobile data working (it happened just twice here in months)
Hi @Alberto97 I was having Night Light in quick tiles in your 14 Dec Unofficial build but I can't see the tile in Official One??
drkhalidomer said:
Hi @Alberto97 I was having Night Light in quick tiles in your 14 Dec Unofficial build but I can't see the tile in Official One??
Click to expand...
Click to collapse
I did not release anything that day, that is a CM13 feature that is coming back anyway
Alberto97 said:
I did not release anything that day, that is a CM13 feature that is coming back anyway
Click to expand...
Click to collapse
Thanks @Alberto97 for the prompt reply ! Could be coz of some other mod I had flashed ! Can I expect that in future builds ??
Excuse me, but what is the route to turn off led on charge? (Didn´t see this thread and post same question on original)
I've already figured it out. From the search option - enter (ba) - Battery light - turn off
Fede79 said:
Excuse me, but what is the route to turn off led on charge? (Didn´t see this thread and post same question on original)
Click to expand...
Click to collapse
Settings -> Notifications -> Configure (gear icon in the top right) -> Battery light -> toggle the switch.
is audio fx operational?
I can't see any difference in audio.If it is not working removal from the builds is a good option or not?
Alberto97 said:
Use this thread for questions, help and anything else about LineageOS that does not belong to the ROM development itself, thank you.
FAQs
Does LineageOS support VoLTE? YES
If I install LineageOS will I lose MotoActions? We have our own implementation for MotoActions configurable under Settings -> Gestures, so the answer is No
Your ROM is unrooted, can I install SuperSU? We discourage SuperSU usage, flash our su package (arm) and then enable root access from Settings -> Developer options.
Click to expand...
Click to collapse
Hi I really appreciate your work. Although I would want to know if in future there will be an option to disable one SIM in dual SIM phones.
You have any idea how to disable single SIM?
Thanks
Can i dirty flash over unofficial build?
h0ttentot said:
Can i dirty flash over unofficial build?
Click to expand...
Click to collapse
No.. u cant..
Sent from my Pixel using Tapatalk
vj9716 said:
Hi I really appreciate your work. Although I would want to know if in future there will be an option to disable one SIM in dual SIM phones.
You have any idea how to disable single SIM?
Thanks
Click to expand...
Click to collapse
That feature generally relies on closed source qcom components though looks like motorola uses its own implementation. Additionally I have a single sim variant of osprey and I don't want to include anymore components that I can't test, I already did a big mistake with IMS/VoLTE support.
Are there problems with WiFi?
I have the (XT1543)
this rom have substratum support?
This may actually be a development question, but I'm going to err on the side of caution and post here first, then see if @Alberto97 thinks it's worth elevating to the dev thread.
I have an XT1540 2GB/16GB osprey on MetroPCS (T-Mobile MVNO reseller in the US), and I had successfully managed to get Pokemon Go working for several versions of the 7.1 releases.
Specifically using iSu by @bhb27 (thanks! ), which renames the su binaries when toggled on, and then puts them back when toggled off. No Xposed framework (I know, I know; don't even think about it near a CM development thread), no Magisk, no Chainfire or phh SuperSU... always making backups with Titanium Backup then restoring things one at a time (and re-doing system settings, not restoring) after a full wipe & clean flash. Using TWRP 3.0.2-r5 and a known-good MicroSD card.
Versions where I think it worked:
CM 14.1 (Dec 25 & 27 builds)
Lineage Unofficial (Jan 12, 13, & 14 builds - I know those were supposed to be for just the CDMA variant, but they also seemed to have the side effect of making the GPS and PoGo work again)
Versions where it hasn't worked:
LineageOS Unofficial (Jan 10 and before): Would NEVER get a GPS fix, no matter how long I left it running. GPS Status was able to get a location properly, even in device-only mode; it just wasn't passing through.
LineageOS Official (Jan 25): Gets a GPS fix, but seems to fail SafetyNet attestation, both with official root add-on from lineageos.org applied then hidden with iSu, and with a fresh install that doesn't even have the root add-on package installed.
Again, that's with internal storage/data/system/cache/dalvik/your mom all wiped and a clean install.
So, CM/LOS used to pass SafetyNet, at least well enough for Pokemon Go to successfully sign in with my Google account credentials, merely by renaming/deleting the su binaries. Now it doesn't. Is that due to how the add-on package applies root vs. how it was baked-in before? Any recommendations on what to try? I know it's not everyone's highest priority, but my wife & I enjoy playing when we go for a walk, so being able to continue doing a favorite activity on my favorite ROM is something I'd appreciate immensely.
Is there any way to record on 60fps like in Cm13?
If I flash this lineage rom using twrp , will I lose root access?? If yes, then how will I root again? Pls help... And what are the things which are not working in this rom..?
UtkKing said:
If I flash this lineage rom using twrp , will I lose root access?? If yes, then how will I root again? Pls help... And what are the things which are not working in this rom..?
Click to expand...
Click to collapse
Yes if you flash lineage you will not have root access as the ROM does not have root built-in. You have to flash lineage provided root zip or SuperSU 2.79+ after flashing ROM+Gapps.
UtkKing said:
If I flash this lineage rom using twrp , will I lose root access?? If yes, then how will I root again? Pls help... And what are the things which are not working in this rom..?
Click to expand...
Click to collapse
Hi, please read at least a few posts back before posting. Everything you asked is explained in OP. Thanks.
This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.
This is not a guide as such but more of direction to other peoples hard work and effort. I am not a developer, just an experimenter!
Main Credits - @MishaalRahman and @phhusson.
For me one of the main selling points of the Mediapad M5 was being Project Treble enabled. Being a big Nexus/Pixel fan I am not particularly fond of EMUI.
So after reading this detailed and clear guide by Mishaal Rahman http://www.xda-developers.com/flash-generic-system-image-project-treble-device/, I was able to successfully install an AOSP Generic System Image by phhusion http://forum.xda-developers.com/project-treble/trebleenabled-device-development/experimental-phh-treble-t3709659
My device - CMR-W09 (10.8" non pro wifi).
I flashed v17 with Gapps and SU and apart from an Android System error upon boot it seems to work ok. I have not had much time to play with it but so far Wifi, Bluetooth, sound, camera, fingerprint sensor, MTP and SD card appear to be working. I had issues with google play not downloading apps but worked after clearing data/cache on google play and google play services. Also have issues with superuser force closing.
For the nervous and unsure, you can easily return to stock Huawei firmware by flashing your devices stock system.img in fastboot.
Obviously bootloader needs to be unlocked see guide - https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 by @Apo11on. You can use Apo11on's root guide to download your firmware to get your stock system.img.
OEM needs to be disabled in developer options.
It is best to factory reset via recovery mode and then boot straight into bootloader to keep FRP unlocked.
Do this at your own risk but please read all the available information and guides on XDA.
pphusion has made other Project Treble roms but I have yet to try them. Hopefully it would be nice if someone could fully develop Lineage for this device.
which rom did you use ? the A/B one or A only ?
It's an A-only device.
I tried AOSP with GAPPS and SU but SuperSU shows the su binary as being occupied through several reboots. Getting the Lineage GSI now and will root with magisk.
Edit:
Blah... Lineage is not an option until we have twrp :/ (at least for me) No way to install GAPPS.
Edit:
SU works with phh's super user available from the play store.
Yes i have the AOSP one now on my AL-09 and it works fine till now. Bugs : home Button not working but fingerprint works, supersu with the phhs one works. Bluetooth sometimes gives an error message. Battery drain is a little bit high. I installed the Huawei camera apk from treble forum and This works also good.
Another Bug is Apps sometimes force closing but Not often.
How is Lineage performing?
A little bit off topic, but how did you unlock the bootloader on the Wifi only version since the website for the code is offline for a few weeks now?
Thanks in advance.
Fantastic to see that Treble works.
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
fargonaz said:
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
Click to expand...
Click to collapse
I understand, Do you think it gets more stable for our device in the future?
florian-m19 said:
I understand, Do you think it gets more stable for our device in the future?
Click to expand...
Click to collapse
I think so, if you look at the github comments there is a huawei phone having the same problem, so as long as a phone is having problems it should get fixed
We would like some screenshots to see if this is real @AndDiSa @rcstar6696 @phhusson @MishaalRahman
Just installed it, attached a few screenshots. Haven't tested it a lot, but it boots.
Wie are Not joking, its real ??
Delete, double post
I will be getting my Mediapad M5 8.4 tomorrow and will be flashing the AOSP treble build straight away. Just a heads up a updated build has just been posted with some Huawei related fixes.
i flash it now, and give feedback tomorrow
I flashed the new one with gapps and su, and for the sht-l09 there is no working bluetooth, so that's as far as I go. It will be nice when the BT is fixed for this device.
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
florian-m19 said:
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
Click to expand...
Click to collapse
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
darren1 said:
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
Click to expand...
Click to collapse
yes it is on interactive, should i change this ?
florian-m19 said:
yes it is on interactive, should i change this ?
Click to expand...
Click to collapse
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
darren1 said:
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
Click to expand...
Click to collapse
okay i change it in helix engine to ondemand and the suspend engine is now on powersafe.
XC/KUGO/F5321 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device crashes and reboots (mostly happens on demanding tasks)
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-06-16
Last Updated 2019-06-16
so are the micro lags fixed or still happening? there were slow downs and microlags on on games like clash royale etc... not as smooth as stock
This is excellent news! For those of us coming from 8.1 should we dirty flash (along with dsp-label-fixer) or is full data wipe required?
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Bluestar01 said:
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Click to expand...
Click to collapse
yes
official builds are signed and hence not really compatible with homemade
oshmoun said:
yes
official builds are signed and hence not really compatible with homemade
Click to expand...
Click to collapse
thank you, clean flash and is working
Great work! thanks for taking time to upgrade this ROM to Pie.
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
EDIT: GPS works
EDIT 2: GPS has a mind of its own and will not work except for the time when it does, currently investigating (probably something wrong with my phone)
ardylemon said:
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
Click to expand...
Click to collapse
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
droncheg said:
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
Click to expand...
Click to collapse
Thank you, I also got it to work after waiting a while, enabling mobile data as well as derping around with A-GPS settings in the process appears to have worked (not sure which, though). For future reference, my phone locked in after detecting at least 8 satellites with ~20% signal.
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
I've not this problem, for me all is working well and smooth (the only problem is quickswitch magisk module not working).
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
The Unofficial version of OmniROM by HarryHarryHarry had a similar issue, the fix was to first flash the latest stock ftf image (ends with .118), flash twrp and do a clean install of the rom. I would think this fix is going to work for this version too.
I'm currently running the Omnirom 8.1, and I just got a pushed message from OpenDelta on the phone itself:
Update ready to download
omni-9-20190616-kugo-WEEKLY
Click to expand...
Click to collapse
Can I update to Omnirom 9 from the phone itself by running that? Or must I download the rom on my computer and install it the normal way?
Great I will try this very soon!
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
In regards to the device crashing/rebooting issue. Does underclocking help at all?
lapucelle2 said:
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
Click to expand...
Click to collapse
Did that work? I've got the same issue
After updating to the latest weekly today, some apps got uninstalled again. I dad this behaviour also with the test builds before.
can't find stock rom yet i gave up upgrade to 9.0
Mietjelan said:
Did that work? I've got the same issue
Click to expand...
Click to collapse
can't find stock rom yet i gave up upgrade to 9.0
lapucelle2 said:
can't find stock rom yet i gave up upgrade to 9.0
Click to expand...
Click to collapse
I can't find how to install it either, all that flashtool crap isn't working...