{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_motorola_surnia
Kernel source code: LineageOS/android_kernel_motorola_msm8916
Working:
Camera (and flashlight)
WiFi
Battery LED
Bluetooth
Telephony (Calls) & Data
Audio (Record and Playback)
Video Playback
Sensors
GPS
VoLTE
Bugs:
Encryption
Selinux enforcing
Ui is laggy
Nothing (?)
Downloads:
Download
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery
Format /system, /data and /cache
Install LineageOS zip package
Important notes:
* Required * firmware version must be based on Marshmallow/Lollipop
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if Stockrom was previously installed and device was encrypted.
Credits & collaborations:
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
DONATIONS : Paypal
Contributors
althafvly, chil360, squid2, jeferson1979, Alberto97
Source Code: https://github.com/MOTO-M8916
Reserved
It's amazing to see such an old device get the latest Android version. Thank you so much for keeping the device alive! I will try the ROM tommorow.
Surnia with Android 12... I dont believe it ! OMG...
Any plans to become official?
Unlocked a bootloader for the first time and installed 19.0 to my XT1527 (US) with stock Lollipop 5.1 which had been upgraded from 5.02 OTA. Wasn't able to use ADB to sideload with the 19.0 recovery but the 17.1 recovery was able to sideload this 19.0 ROM.
As part of the 3g shutdown, US carriers are restricting LTE access to VoLTE-capable phones. I was curious to see if my XT1527 could survive these restrictions with a fresh VoLTE-capable OS. AT&T has a whitelist and surnia didn't make the cut. Not sure how AT&T determines if a phone is VoLTE-capable but it might not permit XT1527 access regardless of the OS or VoLTE capabilities.
Quick answer: Not yet and perhaps not ever. Since early March 2022, I've not been able to access LTE on Stock Android 5.1, official Lineage 17.1 or unofficial 19.0. I have 2g/3g only without MMS. But other Lineage features work as advertised. It's pretty fast without Gapps. Both the unofficial 17.1 and the unofficial 19.0 builds are impressive development efforts.
There is no stock Marshmallow 6.0 for the US XT 1527 and the upgrade from 5.02 to 5.1 disabled band 12 from US phones. Evidently, Moto didn't want the hassle of certifying the XT 1527 for VoLTE and instead chose to disable band 12 at the request of one major carrier that wanted to use 12 for VoLTE traffic. I'm wondering if that could cause LTE-access problems when flashing 19.0 on top of 5.1. The official 17.0 instructions were clear that we should start with stock Marshmallow but I wasn't sure about trying non-US ROMs.
Perhaps reinstalling Lineage 17.1 starting with a non-US 6.0 (or US 5.02) stock ROM would restore LTE. Another possibility is to switch within my MVNO to a T-mobile SIM (another major US carrier.) Anyone know if any US carrier will permit surnia access to LTE on any OS after the 3g shutdown is complete?
Also wondering if VoLTE is implemented in a proprietary way by US carriers that hinders open source OS development work.
Thanks again for a nice effort. The XT1527 is the only smartphone I've ever used...will hate to give it up if/when both LTE and 3g access are removed.
I have tried this rom today and most stuff works fine. i have encountered one issue with the "3 button" controls setting turned on, the trebuchet launcher crashes if you try to see all the open apps. This doesn't occur if i use the " nova launcher". Keep up the good work.
Updated to 12L (check OP for link)
- Fixed mobiledata
The "laggy UI" seemed to get worse over time in the week or so that I tried the first cut at 19.0 for Moto E 2015. Even though I didn't load extra software, by the end of the week it struggled to bring up a PIN-number screen unlock without displaying it on the Lineage logo simultaneously. I don't remember it doing that after 19.0 was first installed. Perhaps freeing up memory or other resources when unneeded would improve UI performance.
tales59 said:
Also wondering if VoLTE is implemented in a proprietary way by US carriers that hinders open source OS development work.
Click to expand...
Click to collapse
Not just US carriers. As far as I know, there does not exist any fully open-source VoLTE implementation on any phone, for any carrier, anywhere in the world.
My phone has a low battery
I think I need to change it or maybe I should buy a used E2.
What do you recommend?
I hope it will be supported for years to come. I don't want to leave it. For a basic use, it is the top. It is comfortable in the hands. I am lost with recent smartphones. Too big for my taste.
We need more E2
Thanks for the support!
nabav said:
My phone has a low battery
I think I need to change it or maybe I should buy a used E2.
What do you recommend?
I hope it will be supported for years to come. I don't want to leave it. For a basic use, it is the top. It is comfortable in the hands. I am lost with recent smartphones. Too big for my taste.
We need more E2
Thanks for the support!
Click to expand...
Click to collapse
There are new E2 batteries available on both eBay and Amazon for around $6, and that typically includes a small toolkit for the job. Here is a listing for a brand name FT-40 battery for the E2 for $5.42 w/free shipping.
Battery FT-40 SNN5955A For Motorola XT1526 XT1528 Moto E XT1527 2nd Original 9322143822 | eBay
Find many great new & used options and get the best deals for Battery FT-40 SNN5955A For Motorola XT1526 XT1528 Moto E XT1527 2nd Original at the best online prices at eBay! Free shipping for many products!
www.ebay.com
Viva La Android said:
There are new E2 batteries available...
Click to expand...
Click to collapse
For sure, but I need an hot air gun to detach the screen before replacing the battery. I don't know if I can do without it.
nabav said:
For sure, but I need an hot air gun to detach the screen before replacing the battery. I don't know if I can do without it.
Click to expand...
Click to collapse
The only tools I used were thin plastic edging tools (resemble guitar picks), a pry tool, and a T4 Torx security screwdriver. When reassembling, some 3M adhesive strips work nicely for getting the display back nice and snug. A regular hair dryer can, of course, be used to warm the edges of the display first, in order to loosen the underlying adhesive and make prying.a bit easier. On the three Moto E 2nd Gens to which I've done repairs, I haven't needed to resort to heating the screen first.
Viva La Android said:
The only tools I used were thin plastic edging tools (resemble guitar picks), a pry tool, and a T4 Torx security screwdriver. When reassembling, some 3M adhesive strips work nicely for getting the display back nice and snug. A regular hair dryer can, of course, be used to warm the edges of the display first, in order to loosen the underlying adhesive and make prying.a bit easier. On the three Moto E 2nd Gens to which I've done repairs, I haven't needed to resort to heating the screen first.
Click to expand...
Click to collapse
Also, I should mention that when you are able to run the plastic edging tool all the way around the screen -- essentially breaking the seal -- use a playing card to assist you in prying the display from the phone body. The E2, as you probably know, has a LCD + touch screen digitizer display assembly. A playing card helps greatly with getting under the digitizer versus the edge of the LCD, which can be ripped from the digitizer if you're not careful.
OP, I do apologize for posting off topic in your thread.
I'm currently running LineageOS 17.1 with A10 and doing great. I would like to try 19.1 with A12. But I have a doubt because the opengapps.org site only shows gaspps up to A11 and this ROM is A12. Could you help me and tell me if they exist and where I can download the gapps for A12
jonta0 said:
Surnia with Android 12... I dont believe it ! OMG...
Any plans to become official?
Click to expand...
Click to collapse
God wants. Since we stayed in the official 17.1 with android 10
Viva La Android said:
The only tools I used were thin plastic edging tools (resemble guitar picks), a pry tool, and a T4 Torx security screwdriver. When reassembling, some 3M adhesive strips work nicely for getting the display back nice and snug. A regular hair dryer can, of course, be used to warm the edges of the display first, in order to loosen the underlying adhesive and make prying.a bit easier. On the three Moto E 2nd Gens to which I've done repairs, I haven't needed to resort to heating the screen first.
Click to expand...
Click to collapse
I have some tools but they are very cheap, including a torx and a plastic triangle, so pretty useless. I think I can use an old phone card. Let's say that the most difficult task is to detach the screen, then I hope to be able to remove it with the tools I have. I have to buy 3M double-sided tape or glue. as well. I will keep you informed as soon as I have the spare parts.
Thank you for your suggestion
nabav said:
I have some tools but they are very cheap, including a torx and a plastic triangle, so pretty useless. I think I can use an old phone card. Let's say that the most difficult task is to detach the screen, then I hope to be able to remove it with the tools I have. I have to buy 3M double-sided tape or glue. as well. I will keep you informed as soon as I have the spare parts.
Thank you for your suggestion
Click to expand...
Click to collapse
No problem. Yeah once you get the screen detached from the midframe, the T4 Torx will remove all screws holding the logic board in place, allowing you to then access the battery Take care when detaching.the display not to rip the flex cable connecting the display to the board. Pry tools won't get anywhere near it, but when prying it loose use caution .
I put ROM 19.1 to test and had to restore the save again and continue with the official version 17.1. This 19.1 everything worked for me but when I open the PHONE application, MESSAGES and CONTACTS close automatically. Turn back because without these applications it is impossible to have a mobile.
Is unlocking the bootloader always to be done? I have lollypop in this other phone, not Marshmallow.
Related
This is the latest firmware I coudl find on any site. It was Asian so I converted it to work with the P600UE (US Based P600's and other variants).
Features:
Made Compatible with US devices (may work on other regions).
Removed Knox and proloaded Kisok mode
Pre-rooted with SuperSU
Odex or De-odex'ed
Zip Aligned
Set Google as home page
Busybox
init.d Support
Removed Chinese Keyboard.
No other changes or modifications.
Once again, this is an untouched stock ROM other than what is listed. There are no tweaks or enhancements.
It took me 2 days to figure out how to get around the regional coding on the new Samsung devices so please hit Thanks if you download.
Downloads:
Odex: Stock-Root-Odex-P600ZTUBML1.zip - 1.22 GB
De-Odex: Stock-Root-De-Odex-P600ZTUBML1.zip - 1.22 GB
Please hit thanks. Tips are aprpeciated
Sharing Policy
The spirit of Open Source is to share your knowledge and files with the rest of the world so they can improve on what you do when possible. This is also my philosophy and I would never compromise that!
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credits!
Do not use my work if you cannot give proper credits!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
However this does not include my CleanROM series of ROMS. Please do not use those without contacting me first!
This ROM is not a CleanROM. Its a stock rooted and all yours!
Hit Thanks!
Again...
First! <----always wanted to post this.
Let me do a nandroid backup and I'll flash this tonight when I'm home.
Are you looking for anything specific?
Update @ approximately 2pm PST
FYI: This download took well over an hour.
Thanks, 5 stars!
Sent from my SM-N900P
awesome thanks !
harrychimp said:
First! <----always wanted to post this.
Let me do a nandroid backup and I'll flash this tonight when I'm home.
Are you looking for anything specific?
Update @ approximately 2pm PST
FYI: This download took well over an hour.
Click to expand...
Click to collapse
Well, I just want to make sure everything works. It was a big learning experieence about the regional coding files and the SEA policies which I finally figured out.
So if you can test apps in the play store, over all functionality type thing. Looking for things like "Not supported in your region" errors although I doubt it (USA Regions only, other regions I cannot support).
IM sure its good as I ran with it for two days and liked it.
scrosler said:
Well, I just want to make sure everything works. It was a big learning experieence about the regional coding files and the SEA policies which I finally figured out.
So if you can test apps in the play store, over all functionality type thing. Looking for things like "Not supported in your region" errors although I doubt it (USA Regions only, other regions I cannot support).
IM sure its good as I ran with it for two days and liked it.
Click to expand...
Click to collapse
Google play services was force closing but updated all my apps and it went away
vincey2kr1 said:
Google play services was force closing but updated all my apps and it went away
Click to expand...
Click to collapse
Sadly that is a typical issue with play services.
They try to push that at the same time the push the apps and it can cause a mess.
Google needs to get it together... But then again, I dont think they made Android for the Crack Flashing crew.
When I was playing with this I think it felt a little smoother than the MK1 base.
Does anyone have any input on that?
And what do you think of the Autobrightness control?
Why did you convert a stock Asian rom to be compatible with US/EU version of P600?
Haven't they the same hardware or product code (SM-P600)?
I ask you this since I ordered a note 2014 from Singapore and I would flash an European stock rom with my country's csc.
Do you think it's not possible?
Samsung SM-P9005 - Tapatalk
Here's some of my thoughts about the Asian ML1 version.
Thank you very much for sharing this ROM with us.
{
"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"
}
One more thing to add:
It seems there is a significant lag for the screen to turn on after the tablet was off for more than a few minutes.
Also tested the magnetic cover on both Poetic cases I own. The tablet display turns on and off when cover is opened and closed.
mouse100 said:
Why did you convert a stock Asian rom to be compatible with US/EU version of P600?
Haven't they the same hardware or product code (SM-P600)?
I ask you this since I ordered a note 2014 from Singapore and I would flash an European stock rom with my country's csc.
Do you think it's not possible?
Samsung SM-P9005 - Tapatalk
Click to expand...
Click to collapse
For whatever reasons Samsung seems to have locked them like they did with the phones and sims. I beleive, but cannot prove for fact, that they are using the same "technology" from the Note 3. You can read more about it here: Samsung’s Regional SIM-Lock: The Stupidest Thing Ever?
Now I dont know for fact, so take it with a grain of salt, but look at the first digit of the firmware and that is the region. Take look here on THIS PAGE for the region and the firmware versions. You will see a pattern.
It seems, Arabian devices all start with X, European based devices start with U, US based devices start with U as well. All Asian devices start with Z. But what throws me off is not all countries seem to be in the region you would expect. So I really am not sure. I just now that some people cant use my ROM very well and others can.
I know that i could not get the ZT base to work until I swapped out portions of the RAM disk and some really strange files in the /system partition which I beleive are tied to the ram disk files which then seem to tie to the region. THIS IS ALL SPECULATION on my behalf. I wont know unless I have a device from Asia to test or someone that knows more about Samsung product codes can elaborate.
Now, I cant honestly tell you that they wont be able to cross but I can tell you I had to tear out some files from the UE based ROM (United States) and replace those files in the ZT based ROM (Tiawan).
Like I said, take it with a grain of salt.
When you get your device send me a PM so I can have you look at things and quantify my thoughts. All my theory are based on my physical US Based Device and the troubles I had getting the Asian based ROM to flash.
harrychimp said:
Here's some of my thoughts about the Asian ML1 version.
Thank you very much for sharing this ROM with us.
View attachment 2501414
One more thing to add:
It seems there is a significant lag for the screen to turn on after the tablet was off for more than a few minutes.
Also tested the magnetic cover on both Poetic cases I own. The tablet display turns on and off when cover is opened and closed.
Click to expand...
Click to collapse
Although I cannot read your hand writing I did seem like a positive tone? lol
The lag on wake is by design. I know, strange... But thats how any Exnyos process based device is.
Refernce any article in this quick Google Search and you will see it covers almost every Exnyos device Samsung makes. Not just the Note 10.1.
We will need to enlist a real good kernel developer to remove that lag. You can read more about it in my CleanROM thread as we were just discussing it there...
But in a nut shell, the tablet goes into deep sleep and it has to be woken up. This is done to conserve battery.
I also tested the wake lag against stock MK1 base and its actually improved. At least form my testing anyways. Take it with a grain of salt as I am an old man and cant count very well
Hey this is exactly what i was looking for.
My brother and I bought our dad this tablet from the US and the first thing I did was root it as usual with all the other android devices in our house haha.. but as usual after rooting and installing a custom recovery you cannot do OTA's.
I would like to know will you be keeping this stock and maintaining this as samsung pushes updates. the first thing my dad did, was check if he could do auto updates and it said no tablet is modified. So I told him I would have to do it manually.
Many thanks in advance.
Also is this ML1 the latest release by Samsung?
scrosler said:
Although I cannot read your hand writing I did seem like a positive tone? lol
The lag on wake is by design. I know, strange... But thats how any Exnyos process based device is.
Refernce any article in this quick Google Search and you will see it covers almost every Exnyos device Samsung makes. Not just the Note 10.1.
We will need to enlist a real good kernel developer to remove that lag. You can read more about it in my CleanROM thread as we were just discussing it there...
But in a nut shell, the tablet goes into deep sleep and it has to be woken up. This is done to conserve battery.
I also tested the wake lag against stock MK1 base and its actually improved. At least form my testing anyways. Take it with a grain of salt as I am an old man and cant count very well
Click to expand...
Click to collapse
The feedback of your ML1 stock ROM was positive. All apps I used simply worked. There was nothing unusual about any of the apps, including no force closes.
Touchwiz launcher also seemed quicker when scrolling through the home pages and application pages. I plan to do a Titanium backup and make this my daily ROM for a few days (or longer).
As for the lag when turning on the screen, I was only making an observation. It was neither a positive or negative comment about the ROM. I prefer the tablet to go into deep sleep mode as fast as possible to conserve battery life. So an extra half second or so for the display screen to turn on is an easy tradeoff.
kazemitsui said:
Hey this is exactly what i was looking for.
My brother and I bought our dad this tablet from the US and the first thing I did was root it as usual with all the other android devices in our house haha.. but as usual after rooting and installing a custom recovery you cannot do OTA's.
I would like to know will you be keeping this stock and maintaining this as samsung pushes updates. the first thing my dad did, was check if he could do auto updates and it said no tablet is modified. So I told him I would have to do it manually.
Many thanks in advance.
Also is this ML1 the latest release by Samsung?
Click to expand...
Click to collapse
I will more than likely be doing stock roots for any update I can for the duration of tablet owner ship.
As the very first line of the opening post stated; this is the latest build I can find anywhere on the internet.
If anyone ever finds anything newer than what I have they normally will post in one of my threads or will send me a PM. Plus I scour certain firmware sites daily.
harrychimp said:
The feedback of your ML1 stock ROM was positive. All apps I used simply worked. There was nothing unusual about any of the apps, including no force closes.
Touchwiz launcher also seemed quicker when scrolling through the home pages and application pages. I plan to do a Titanium backup and make this my daily ROM for a few days (or longer).
As for the lag when turning on the screen, I was only making an observation. It was neither a positive or negative comment about the ROM. I prefer the tablet to go into deep sleep mode as fast as possible to conserve battery life. So an extra half second or so for the display screen to turn on is an easy tradeoff.
Click to expand...
Click to collapse
Good good!
IM going to chop this up into CleanROM within the next couple days.
I also see a few performance gains as far as the launcher, etc.
Hey scott. I havent flashed your rom yet but when I flashed it as a firmware I seem to have some wifi dropping issues. Did you notice this or did some of your hacks change the wifi?
Sent from my SM-N900V using Tapatalk
jbeitel said:
Hey scott. I havent flashed your rom yet but when I flashed it as a firmware I seem to have some wifi dropping issues. Did you notice this or did some of your hacks change the wifi?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Nah, I see some changes in the system dealing specificallyh with WiFi and Bluetooth but I have not had an issue with WiFi (nor do I 100% understand teh changes between MK1 and ML1).
However, the bootlaoder may have also attributed to this. I made this rom so it would run with the MK1 US Bootloader.
I would Odin MK1 then you should be able to flash this. But as far as WiFi drops for me personally, nah. Seems good.
Anyone else see any WiFi issues?
scrosler said:
Nah, I see some changes in the system dealing specificallyh with WiFi and Bluetooth but I have not had an issue with WiFi (nor do I 100% understand teh changes between MK1 and ML1).
However, the bootlaoder may have also attributed to this. I made this rom so it would run with the MK1 US Bootloader.
I would Odin MK1 then you should be able to flash this. But as far as WiFi drops for me personally, nah. Seems good.
Anyone else see any WiFi issues?
Click to expand...
Click to collapse
That's great, i'll be sure to try it when i get home then.
YOU HAVE NOW BEEN CARBONIZED
Built from the Carbon source, these unofficial builds will be updated weekly. Maybe more if time permits or there are any huge changes to be incorporated. Built specifically for our devices, no ports here anymore. This should allow it to run a bit better than a rom that was technically built for another device.
And now, on with the show!
About Carbon
{
"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"
}
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Carbon Features
All of our features can be found on our site here:
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
***NOW BUILT WITH ArchiDroid OPTIMIZATION STARTING 11/07***
Many thanks to @JustArchi for his commit regarding optimizations in Android builds. What are these optimizations? Check out THIS THREAD for more details on what this entails. In most basic terms, this optimizes code within the build a lot more than the traditional flags set by the code I build from. You may not see a doubled AnTuTu score, or doubled battery life. But this provides a lot more stability and smoothness than simply using the Sabermod toolchain that is also included in these builds. So props to him for this commit. Go give the man some thanks!
Special Thanks
Let me do this first and foremost before moving on with the downloads and installation instructions. This would not be possible without the help and guidance of a few other talented builders here in our community, and without the help of those who tested this before it was posted.
Thanks to @rogersb11 and @cyril279 for helping me out along the way. Their guidance and support have been most beneficial, and without that help, this thread wouldn't be here. So if you thank me, be sure to thank them too!
Thanks to the entire Carbon Team for the hard work they put into building such an amazing AOSP rom.
Thanks to my testers, @cyril279, @edwin270, @rogersb11 and @dsteele for being brave enough to be the first people outside of myself to take this new build for a spin.
To anyone else who has helped me along the way in my Android experience and journey from noob to only partially, just a bit of a noob. Your guidance and support has been appreciated more than you could know.
Download and Installation Instructions
As always, neither I, nor the people thanked in this thread, nor your neighbor are responsible for anything that may happen to your device including, but certainly not limited to: Soft Brick, Hard Brick, Exploding Batteries, One Fish, Two Fish, Red Fish, Blue Fish, raining porcupines, or male patterned baldness.
**IMPORTANT: If you are coming from ICS or JB, you MUST upgrade your recovery BEFORE flashing this rom. See below for compatible recoveries**
CWM - 6.0.4.4+
TWRP - 2.6.3.0+
For SGH-S959G
CWM - 6.0.4.5 from here
TWRP - 2.6.3.0 from here
1) Download the latest build from here (Current Build: 12/08 ). Older builds can be found here.
2) Download the Gapps pack of your choice. (I personally use Slim Minimal 4.4.4 which you can find here). But feel free to use whichever Gapps package you prefer.
3) FULL WIPE if coming from any other rom. If updating, wipe cache/dalvic before flashing, unless stated to do a full wipe.
4) Flash the ROM package
5) Flash Gapps package of your choice
6) (Optional) Reboot recovery, wipe dalvic/cache. (Recommended if you are coming from a custom kernel build.
7) Reboot device and enjoy the goodness.
SPECIAL NOTES
This will flash with the stock CM kernel with CWM Recovery, which many people find a little laggy. There are custom kernels in the forums that you can flash after the rom if you want more control, performance, stability, etc.
This is built straight from the source code found on the CarbonDev Github. The only things that have been changed are the removal of CarbonDelta and ROM Stats. Since these are unofficial builds, not supported by the Carbon team, these two apps really serve us no purpose. All updates will need to be flashed through recovery.
All bugs or questions should be reported to THIS THREAD ONLY. Do not send questions to the Carbon Team as this is not an officially supported device anymore. So don't bother them. Bother me instead.
For general CarbonRom questions, check out the FAQ.
That's all I have for now. If you enjoy this rom, please hit that thanks button and inflate my ego a little bit.
Happy flashing!
ROM: CarbonRom (Unofficial Builds)
Android Version: 4.4.4
Kernel: Stock CM Kernel Source
Built by: @TheGeekyNimrod
Reserved because you never know when you might want that second post spot.
Here we go...booting as I type...
desteele said:
Here we go...booting as I type...
Click to expand...
Click to collapse
Woo hoo!
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
Woo hoo!
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
That sounds more like just a bum install of Gapps. Especially if it didn't ask for Google Account right off the bat. I've had that happen before. Usually not a rom or Gapps package issue, but just something hanging in the flashing process.
Glad to hear everything else went fine. I'll do another fresh install on mine in the morning and see if the same issue crops up.
Sent from my SAMSUNG-SGH-I747
desteele said:
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
Click to expand...
Click to collapse
For network I am always on 2g unless i do want to use the phone data( which i mostly never use, always on wifi). Sure 3g signal is not so strong from within your room.
When done with rom flash, I made it boot first. Then went ahead to set it up without google account, when back to recovery and flashed gapps.
Finally, after changing to "art" runtime I launched playstore then did setup my google account.
So far, so good............just about to pull my battery stat, to be sure it last as it should be. All my apps are running great so far.
NOTE: be sure to wipe/factory reset 3 times. Since previous gapps could be left untouched. I again make sure i wipe data, cache, dalvik cache again respectively, so to be certain.
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
TheGeekyNimrod said:
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
desteele said:
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
Click to expand...
Click to collapse
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
edwin270 said:
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
Click to expand...
Click to collapse
You can disable it for specific apps from Settings>Apps ... Go over to all apps. Select the app you want to disable it on, select blacklist, and select blacklist from hover.
Sent from my SAMSUNG-SGH-I747
rogersb11 said:
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
Click to expand...
Click to collapse
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
edwin270 said:
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
Click to expand...
Click to collapse
Pocket mode is a lot of what's behind it I think. Using the proximity sensor and turning the screen on. I disable it right off the bat.
Sent from my SAMSUNG-SGH-I747
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
rogersb11 said:
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perhaps I should change up the OP and second post and leave a list of features and such? For granted, the link in the current OP will take you to the Carbon website where it's all listed.
It didn't hit me until I messaged you about the pocket mode. It took me a while after first porting it to realize what was going on. By habit now I always automatically disable it right off the bat when I flash it.
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
TheGeekyNimrod said:
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
Click to expand...
Click to collapse
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
rogersb11 said:
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- I haven't yet. Won't start it till later tonight. I let it run while I'm catching my Zzzzs.
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. Fulmics o), Resurrection Remix, AOSPA, Dirty Unicorns, OwnROM, AICP, AOSPExtended, Lineage, ANTHING!
I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Unscedeo said:
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Click to expand...
Click to collapse
It would be nice, I have the same model. I was thinking about getting into Android development and working on this phone but that'll take a good while, most developers probably looked over this phone since it for unlockable so late and really I think stock is enough. I have it modified for my needs and it's alright. And you would think this model would get some development since it's not tied to a carrier but I guess not. If I find where to start and everything I might work on this device and of somehow I figure things out I'll be in development for at least 2-3 years for this device.
Please make custom ROM for rs988
You're to late Guys. The G5 is almost completely abdoned and the Most Devs (Who had a Choice) are gone. Outdated 7.0 Stock Firmware and a lack of good Sources are killing the Rest. Besides that is asking for any Development on it just crazy. You don't need to ask! If there is nothing, there will come nothing....
Never LG again! To many mistakes and not a piece Developer friendly at all. Try to sell Your G5 and You will See what i mean!
He's right about the lack of good sources I had an H830 and the roms for it take away useful features for the lg g5. And all have the same bugs. I tried them but kept going back to stock.
There used to be a time when custom roms made the phone better. That time seems to have passed, it is getting harder and harder to root carrier phones, not just lg.
The rs988 is a smooth running phone, with root we get full control of our phone. If you are not happy with that feel free to port over a rom, but please stop asking for dev support.
We are on our own with this phone.
I'm kinda glad this phone has been abandoned and looked upon so poorly.
I bought a brand new rs988 build date 3/17 for 249.00 B&H Photo about 6 weeks ago. The build quality is better, the screen is better, and no gps issues.
Since the Nougat update the phone is so much improved but if you don't like Nougat you can always downgrade back to marshmallow. (benefit of unlocked bootloader)
I bought genuine batteries from NewEgg recently for 5.99 a piece.
It's one of the few unlocked phones that work on Verizon.
But for me the "always listing" (just like the pixel) very few phones have that feature. The removable battery, the IR blaster, expandable storage are requirements.
If I need waterproofing I throw on my fre lifeproof I bought new for 20 bucks.
Just because something is hard doesn't mean it's not worth it. This phone has been given up on too quickly.
At the current price I wouldn't be surprised if some come back to it.
Peace
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
wolfu11 said:
I bought genuine batteries from NewEgg recently for 5.99 a piece.
Click to expand...
Click to collapse
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
onestyle007 said:
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
Click to expand...
Click to collapse
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
seraphism said:
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
Click to expand...
Click to collapse
I'm on my phone now,but have some bookmarked on my laptop. When I get home I'll pass some. For starters search XDA and use Google building Android from source, plus go on LineageOS manifest GitHub. Repo sync first,it will take a while. By the way, you'll need a stronger PC or laptop if you want to build fast also Linux or osx or on Windows you'll need Linux in virtual PC. SSD drive recommend.
Unscedeo said:
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Click to expand...
Click to collapse
Unfortunately they are sold out now....
View attachment 4212964
View attachment 4212965
Don't get Me wrong. I've put much efforts into this Phone since i still think it's a good piece of Hardware. I'm also Out of Money so i have to stick with it. But it makes Me crazy sometimes as a Ex Samsung, HTC, SONY and Nexus User/Dev to have a LG.
-The Sources
-The Community (XDA)
-The Bootloader (Recovery Access, Bootloader Message)
-The Build Quality (Light Shadows on the Display, the bottom Gap, Volume Rocker Stucks)
And the most Important Thing - UPDATES
We are using a 2016 Flagship and No Android 7.1? Still?
What about Android 0? Do we get a real Update or just a Copy OS from the V20? Like with the actual/past Updates?
I'm really done with LG. That they ditched us with the Modules is another Big Point for Me as G5 User. I would at least be more happy with a V20 since it wasn't a Joke like the G5....
For those interested, the following LG G5 variants have the same FCC ID of ZNFVS987:
Code:
VS987 - Verizon Wireless variant
US992 - U.S. Cellular variant
RS988 - General North America variant
Presumably, the variants are of the same hardware, but have different firmware.
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Unscedeo said:
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Click to expand...
Click to collapse
When all that is done,well then you or any other developer uses that tree with already synced repo from any of the custom ROMs along with the G5 repos to try and make a build.
First thing's first,to get a device tree. Building a rom from the source comes later, and luckily there's more than one tutorial on how to get it done. Then it's figuring out what doesn't work and how to fix it.
Source?
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Unscedeo said:
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Click to expand...
Click to collapse
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
onestyle007 said:
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
Click to expand...
Click to collapse
Never mind, I figured out how to unpack the boot.img. I now have the basic files created, including AndroidBoard.mk, AndroidProducts.mk, etc. I just created the files that are listed in this tutorial (the one you gave me): https://forum.xda-developers.com/showthread.php?t=2010281
So I also found this on Github, which states that it is the device tree for the RS988: https://github.com/jcadduono/android_device_lge_rs988. I don't know if that is what you want me to make, and if it is, can we use that? If that isn't the right tree, I am currently on writing the BoardConfig.mk file, which is one of the steps in the tutorial mentioned above. it says to use a "cousin device" tree. What should I use for that?
Thanks
Thanks for this..
Again.. thanks for the heads up on how to get the ball rolling on this.. I should have some time to unlock my bootloader and post the boot.img and other necessary files this weekend..
Cheers!
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
Any luck with our rs988? ?
Sent from my SM-G950N using Tapatalk
{
"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"
}
PixelExperience for Note 4
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
SE Linux Permissive
DON'T FLASH GAPPS, ALREADY INCLUDED
Download here
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned
Android OS version: 9.0.0_r35
Security patch level: April 2019
Build author: Inkypen
Source code: https://github.com/PixelExperience
Device tree and kernel: https://github.com/triplr-dev
ROM Developer: jhenrique09
XDA:DevDB Information
Pixel Experience, ROM for the Samsung Galaxy Note 4
Contributors
Inkypen, tripLr, ripee
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-04-29
Last Updated 2019-04-29
File host changed to AFH, download link updated. Should be no more download errors
https://www.androidfilehost.com/?w=files&flid=293509
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
73sydney said:
You have 2 threads for each of your ROM's
This is confusing......
Please chose one and get the mods to remove the duplicates, for everyones sanity, not just mine
Click to expand...
Click to collapse
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Click to expand...
Click to collapse
Inkypen said:
For some reason XDA double posted my build threads. This thread is the one I get updates for, not the other one. Will ask a mod to close the duplicates.
I saw your comments on the other thread, I cannot fathom why you would download a ROM called "Pixel Experience" and then complain about GApps being included! It's quite literally baked into the ROM as you can't experience the Pixel phone which is made by Google, without the Google apps......
Whether it's intentional or not, reading some of you recent posts you come across as a sterotypical "entitled" user. Nobody forced you to download any builds of any ROM, this is a development forum and as such bugs are to expected. Rather than complain about bugs and missing features, send logcats and commits for the features you want to see. Perhaps you should read the standard disclaimer in the first post of every ROM you will ever download, including RR:
Click to expand...
Click to collapse
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
For clarity, heres my exact comments from the duplicate thread, please note that thread also included bug reports which i didnt repeat as they had already been expressed:
Tested this ROM, and heres my thoughts/criticisms:
* Inclusion of some G-Apps, while others which are more critical (Gmail most notably) are missing....for the huge download this oversight is really hard to fathom. 748Mb and no Gmail included? Also missing Android Webview.....kind of important
Instead all the stuff i normally weed out by never selecting it in Aroma G-Apps or usign the debloat magisk module if its built into a ROM is included...Device Health/Digital Wellbeing, and the google search app among them...if i wanted active spyware, id install it....instant downvote
For such a massive download, i cant see anything that would make me bother downloading further builds.
I do appreciate the dev building the ROM but, please consider leaving G-Apps up to the user, and thereby reduce the massive download size....
Update: curiously, some of my magisk modules which work on literally every other ROM ive ever used, fail on this one.....bizarre
About to test the dev's other ROM.....
Update: decided not to, apparently it has some of the same issues. Hope the dev can fix them and test before releasing next time....both ROMS cost me nearly 1.2Gb and both buggy....please test thoroughly before uploading.....
Back to RR for me again....
The best i had test at the moment, Stable, smooth, a Little bit of battery friendly, no overheating, no glitches, the only bug quiet anoying for me it's that I'm unable to activate the phone pressing the home botton, but the rest it's working nice as butter, sometimes the camera freeze taking a picture, thas a Little bit uncomfortable. nice job to all devs working on this rom.
73sydney said:
I suggest you read my comments again as you are totally misrepresenting what i said., i said in short that some critical G-Apps (like Gmail) were missing, yet some others which are eye candy ar eincluded. I suggested you either fix this or leave G-Apps to the user.
Please dont misrepresent me and then talk down to me, and insult me, it will not go well for you.....if you cant take constructive criticism, perhaps ROM development is not for you. These bugs and oversights should have been evident if you tested your ROM before you simply uploaded them....
Click to expand...
Click to collapse
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Inkypen said:
I would also respectfully request you read my comments again. At no point did I insult you, merely highlighted the purpose of XDA forums and reiterate the nature of experimental open source software. Your response reinforces the impression of a stereotypical entitled user, you provided no "constructive" criticism at all, and resorted to threats. I pointed out how your posts could be seen as entitled and demanding and offered an alternative way of expressing your issues. That right there is constructive criticism, whereas moaning about wasted bandwidth is not. If you're not prepared to deal with buggy software and need a production grade OS, perhaps ROM testing is not for you?
To address your specific issues with Pixel Experience:
It boots, phone calls, text messages, mobile data, WiFi, sound, vibrator, touch screen all works. ROM is usable, for a given definition of 'usable' which may or may not match your expectations.
You need to understand the difference between functionality and implementation. Any decisions about GApps and which apps are or are not included is down to Henrique Silva who is the lead developer of PE. There is a good reason why certain apps are not included and that's because some phones don't have a large enough system partition to store all the GApps, so 'core' apps are installed instead. Android WebView isn't even needed if you have Chrome installed, as chromium is installed as WebView provider. Henrique is ensuring functionality on as many phones as possible. My part in this is implementation of said functionality. If WiFi doesn't function as expected or you can't make a phone call then that's up to me to fix. That's where testers come in, a lone developer fuelled by coffee and donuts couldn't possibly envisage and test for every possible use case.
I have no intention of engaging in a tit-for-tat back and forth argument with an anonymous stranger I met on the Internet. If you have something constructive to say about anything related to my implementation of these ROMS, then I'm all ears. Got any suggestions for additional features? Sure, I'll listen and perhaps maybe incorporate it if its within my means, otherwise it needs to go to the lead ROM developer. Want to engage in argument about who said what when? No thanks, got enough stress in my life as it is.
Sincerely, have a nice day. Life is too short to get into random arguments with strangers :good:
Click to expand...
Click to collapse
And again you insult me, among other things calling me "entitled"
You dont get to talk down to me...sorry, thats not happening, maybe when you release something without major issues you might get that privilege, but not before....
Last time, you will insult me and last time i want to hear your crap
Mate, ive flashed, contributed to, and tested more ROMs than youve had hot breakfasts
I wont be testing any more of yours given your attitude..
Especially when you totally discount the fact me asking you to actually test your releases before releasing them as in some countries like mine, bandwidth and data (especially for 700Mb+ ROMS) costs actual money. Your attitude on this, dismissing my data allowance out of hand (moaning about wasted bandwidth )is really quite insulting and rude. Its a valid criticism when its clear you havent properly tested your releases.
Good luck with your work, i wont be testing or recommending anything you release....
And quite frankly if i never come across you again, it will be too soon.....
Get over yourself, you rude self important newbie.
Congrats on being the 1st person ever on my ignore list, fool.
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Raven_999 said:
Can you add "Home to wake" feature to the AEX ROM too?
Thx
Click to expand...
Click to collapse
That's done, and in AEX there's the even the option to toggle it on/off. Builds are running, will upload shortly.
Inkypen said:
If anyone is interested, new builds with May security patch have been uploaded. Home to wake feature has been enabled. Also added tblte and trlteduos builds. https://www.androidfilehost.com/?w=files&flid=293509
Click to expand...
Click to collapse
Can I dirty flash this over the earlier version?
this is probably obvious but i cant find the settings for disabling hardware key lights and is there an on screen nav bar option?
note edge 915f is working hard only problem is the battery is not fully charged 92% 93 (lineage 16 also did not have this problem)
in this rom, camera works. (unlike other pie roms)
edge n915-t
sm-n910u
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Does the second sim working?
sm-n9100 trlteduos
mjhassanli said:
not working on sm-n910u (trhplte) :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably because your phone uses an exynos chipset and this forum is for snapdragon variants. Try this forum instead: https://forum.xda-developers.com/note-4/development
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Jack123hello said:
Just installed this ROM few minutes ago, so far it's smooth and I really like the transition and system animation than LOS one. But I have some questions: does the kernel support F2FS because it seems to bootloop when installed on F2FS? And what how can I root this ROM? Magisk, SuperSU or AddOnSU from LOS?
Click to expand...
Click to collapse
Flash Magisk zip in twrp and then reboot your phone , this is how to root any rom
Hi,
When I read the questions and guides, it seems the Surface Duo can be unlocked and rooted pretty easily.
So I was wondering why there is no custom ROM for this device which is, by all means, not perfect (it has a lot of flaws) but that I consider as at least a refreshing attempt to dig out of the "one glass rectangle touch screen" that we're now used to for years.
Is it beacause there's no love for the device ?
Or is it because Microsoft released absolutely no sources for the internal hardware ?
If there's anyone willing to try, I can offer build server to do it...
And contacts in a community to help iron out problems...
Regards.
Microsoft has indeed released the sources of the internal hardware, or, at the very least, some of it. I don't really know how to determine whether or not all of the drivers are included with the kernel source code. But they do have this kernel source code hosted on GitHub, under a combination of MIT, Apache, and GPL licensing, as well as full instructions on how to build the kernel. The instructions are located at microsoft/surface-duo-oss, and the scripts end up downloading from other microsoft/surface-duo-oss-* repositories. I've not actually tried to build this myself, and I'm not sure what you actually end up with afterwards, whether it is just a kernel, or if it also includes AOSP, and whether or not this can be included in the process of generating another distribution such as Lineage. But, I think this should at least be some information that can be used to at least start the process assuming anyone with existing experience is interested in starting this.
I have seen it expressed elsewhere that one reason people have not created a custom ROM is that android 10 does not have native support for multiscreen devices, while android 11 does. Meanwhile, Microsoft has only released android 10 for the device, and this includes the surface-duo-oss scripts as well, but that there is plans here soon (late September) by Microsoft release android 11 for the Surface Duo.
Fingers crossed! Looking forward to a robust desktop mode and multiple external monitor support like the regular Surface Pro does
Basically a phone that acts like a Surface PC when you dock at home or at work so you can actually work from the device like a normal Surface laptop and then fold and put it in our pockets when we're done working
I know this is an older post but I sure wish someone would go ahead and give me the dummy guide to flash their custom rom!! If anyone needs a duo that thinks they can make it happen I have a spare one..... The left screen is glitching in and out tho.