Database Develop

[ROM][4.4] MIUI v5 [ all moto_msm8960 xHDPI]

{
"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"
}
Overview
This is MIUIv5 for all unlocked-BL xHDPI moto_msm8960 devices.
Being a Beta, everything is assumed to have full functionality, under windows when drives are mounted they may have strange names like "invalid card", this is purely cosmetic.
Working
- Everything...(?)
Not Working
- ?
Download
MOD EDIT Links removed until the ROM is made XDA compliant

great job
i'm waiting to test it
is it support new MI browser with ads filter?

wating for this rom!

any progress on this?

Jl6owa said:
any progress on this?
Click to expand...
Click to collapse
I think it is long process... I tried to port MIUI v5 for XT907 on stock base.. It just wont work.. ((

Update: I've almost completed stock MIUI, I've confirmed it WILL be usable in safestrap devices.
I've almost completed MIUI Kitkat for the whole device tree; it should be available for testing tonight and is very close to being finished right now.
Stock ROM is nearly finished; but I will only be maybe providing OTA update to CM based MIUI because it makes more sense and because having to do stock for locked BL took significantly longer than I expected.
Edit 2: I'm Tquetski, for anyone who doesn't know :<

Uploading now, forgive my ISP speed.
As usual this is a preview, not a final build and broken things can be expected

I keep lying, I fixed all misc errors relating to this build and will proceed with uploading now for various devices, XT926 people be patient please :>

Tried it last night, everything run smooth, especial for alpha.
Not working list is bigger for me : contacts also not working it gives me android.acore error.

problem
Don't boot. Full wipe, but without results
How to install, help please
TWRP, KKBL, Stock

i think you need to be on the old jellybean bootloader.

Jl6owa said:
Tried it last night, everything run smooth, especial for alpha.
Not working list is bigger for me : contacts also not working it gives me android.acore error.
Click to expand...
Click to collapse
Noted, next will resolve these things.
Bit tough patch won't accept multi-base so a lot of this is manual please be patient folks ;/

sunkim50 said:
i think you need to be on the old jellybean bootloader.
Click to expand...
Click to collapse
What? Why? This rom based not on stock?

beefx said:
What? Why? This rom based not on stock?
Click to expand...
Click to collapse
The title and first line conflict but I think it is based on CM.

beefx said:
What? Why? This rom based not on stock?
Click to expand...
Click to collapse
I'm doing AOSP base for every moto_msm8960 AND Stock for this phone.
The thing is that stock can be OTA'd, patch won't accept that so I'm eating the bitter apple first

To install this i uncheck system in mount menu (recovery twrp 2.8).
This rom (based on cm11) is smooth and i love it. Waiting for stable version
Tquerski, thank you!!!

beefx said:
To install this i uncheck system in mount menu (recovery twrp 2.8).
This rom (based on cm11) is smooth and i love it. Waiting for stable version
Tquerski, thank you!!!
Click to expand...
Click to collapse
Everything is now functional beside Update, Backup and Theme-Manager.
Even though I have updated MIUI theme manager seems to force-quit. I'm not entirely sure what to do about it Jing is the only other developer I've heard of resolving this issue. I sent him a PM and hopefully will hear back because I am not really positive what the issue is.
I will avoid posting another build until I can get word on Themes but if a few days go by I'mm just put it up because outside of that everything is pretty much stable

Ok, I got it fixed; I'd like to thank myself because no other dev had input

Downloading)
EDIT: Half day of using and all i can say i like it. working smooth, stable, dont have any force closes, or random reboots. it is my daily driver for now.
and one question, v6 version will come too?

Jl6owa said:
Downloading)
EDIT: Half day of using and all i can say i like it. working smooth, stable, dont have any force closes, or random reboots. it is my daily driver for now.
and one question, v6 version will come too?
Click to expand...
Click to collapse
100% yes

[Unofficial][5.1.1][39A] 7/8 AICP 10.0

.
.
.
.
{
"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"
}
AICP​Android Ice Cold Project​
Installation instructions
First time installing this ROM , or coming from another ROM:
Make sure that you are on VS980 39A modem/bootstack
Ensure your sensors, 4G/LTE, and GPS are working 100%, then backup your phone and EFS partition
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and ROM zip to your internal SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET
- Flash ROM zip
- Flash GApps zip
- Reboot
AICP Source
Kernel Source
5/30 Rom Download
[URL="https://mega.co.nz/#!kdJS1BZB!SId4xazjyCN3AgorEFm0Z3i2ejNLyv_ye5XeNLDHHJI"]7/8 Latest Download
[/URL]Gapps

Reserved
I just built the ROM fresh and have not flashed it yet. It's built with the same sources as my RR rom for the device/kernel so it should all be the same. I'll test later today but I'll leave the link here for people.

First
I'll be sure to check it out later

wasnt this rom still in beta testing? has it even finished testing yet?

Not the same guy building it

ars0n said:
wasnt this rom still in beta testing? has it even finished testing yet?
Click to expand...
Click to collapse
Jpc kernel base if he is saying its the same source as his resurrection remix

Been on this for a few hours an don't have any issues with it. Baseband Unknown is the same as moth other roms and I asked the guy who built the Dirty Unicorns rom how he got it working, so crossing fingers

@ming3r
If he has a fix do share. Because the new lg dev kernel has the same issue

There's a new kernel? WAIT ARE YOU TELLING ME THIS WORKS? https://github.com/lg-devs/android_kernel_lge_msm8974-caf
Unrelated note, I'm not sure if it's a Kernel issue. Both the DU rom and PA all use JPC's kernel.

Only problem I'm having is the play services force closer which I wasn't having on PAC but seemed like I was on everything else

Did you try the gapps I linked? Looks like they fixed some stuff with that Banks one.

@ming3r
Correct, but per rashed&CO. Its not ready for prime time

Lawlrus said:
@ming3r
Correct, but per rashed&CO. Its not ready for prime time
Click to expand...
Click to collapse
Well then. Uh, I may or may not be firing off a build with their sources then...you know, for science.

ming3r said:
Well then. Uh, I may or may not be firing off a build with their sources then...you know, for science.
Click to expand...
Click to collapse
People already have. Might be better to hold off though.
Edit: or at the very least keep it private.

Anyone have working GPS on this ROM??

I'll give this a try in a bit and report back. AICP has always been one of my favorites.

Been a few days and its pretty good so far. Came from PacMan and more things working (minor stuff) with nothing new broken.
GPS works... but it seems more sensitive (random re-routes)... but it might just be my imagination.
THANKS ming3r

What does it mean to make sure all my sensors are working? Is there some mod I need to flash to ensure gps, accelerometers, light sensors work?
Main question is, does HD Calling / advanced calling work on this ROM?

@dr_w
Make sure they're working means flashing a stock 39a ROM if you have not yet, and making sure it rotates a few times before flashing 39a jpc aosp.
I'm not sure if that works on aosp for us or not. Not quite sure there is a way to check.

I'm not sure how much more building I'll be doing for this, but my notes from running this for a few days was that it wasn't smooth enough for me. I frequently got app hangs and force closes for small things, but that may have been the madness caused by Google Play Services. I'm back to RR for now but maybe I'll throw in another build sometime.

Omnirom - preview available

SUPER EARLY RELEASE -
System image ONLY must be flashed thru fastboot - please dont do anything with this if you are not comfortable working in fastboot and restoring factory images.
Here it is
OmniRom for PixelC
Instructions:
Extract zip it is not flashable!
flash system.img with fastboot - ie fastboot flash system system.img
boot twrp
wipe data/cache
flash opengapps - the arm64 android 6.0 version I used stock
restart the device
there will be error dialogs due to bad permissions for the new gapps - its not my fault
tap ok often on those prompts and enter settings between them,
now navigate to apps and tap the three dots at the top left and show system apps
tap setup wizzard and give it all its permissions
give other google services apps permissions as well
enjoy your tablet
Known bugs
Permissions bug with gapps on fresh install
Settings app crashes when you tap the "more" button under interface
Settings performance options can not be set because ramdisk needs to be modified to support the feature

Some screenshots
{
"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"
}
Wallpaper not included grab it here https://www.eso.org/public/usa/images/eso0934a/

Wow ! Congratulations ??

So we are getting a custom ROM finally Thank you very much!
It's a shame: The Pixel C ist the best Android Tablet on the market but it gets almost no community support, because it costs a few bucks more than the usual cheap china crap

i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.

BaristaBot said:
i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.
Click to expand...
Click to collapse
Nav bar tablet mode is a changable feature in settings

I was at work for 13 hours today so no time for anything else, I can upload a system.img tomorrow if anyone is interested it just needs flashed thru fastboot then you gotta manually wipe data and flash gapps and manually set permissions for gapps I'll see how much time I can set aside later this week for a better method. I pulled the source for depth charge and I'll dig in and see if I can figure out how to use it it's kind of annoying that there's no documentation included how hard is it to write a readme sheesh

randomblame said:
Nav bar tablet mode is a changable feature in settings
Click to expand...
Click to collapse
Yeah, scanno originally ported that to Omnirom for the N10 from the Pixel C code base [emoji106]
Sent from my Moto X

does this ROM contain cifs or nfs ?

hagbardceline23 said:
does this ROM contain cifs or nfs ?
Click to expand...
Click to collapse
This isnt a full rom yet so much as a system.img it still uses the stock kernel so you get whatever that supports for now.
I'm uploading JUST the system.img right now I'll link it shortly.
*and it's up check first post.

Awesome!!!

I'm patiently waiting for updates because I'd love to use this without the listed bugs This tablet really needs a bad ass ROM to unlock it's full potential. Not rushing you obviously, good work takes time!
Sent from my Pixel C using Tapatalk

Sorry been swamped I picked up a 2000 beetle for $600 and am ripping the cylinder head off it now, and I've been working my usual 50-60 hours a week too. Ive been running this daily it works great installation is a bit messy tho I'll get to it as soon as I can

My C just arrived today. I'm very happy to see an Omini ROM available. I run Omni as my DD on my Nexus 6. Can't wait to try this.

I am very excited to see where this ROM goes.

Much excite! Impatiently waiting with patience.

BaristaBot said:
i think the bootloader situation is more detrimental to us than the lack of pixel c owners. even chainfire won't mess with it and he owns a pixel.
nice to see a custom rom finally, but it puts the navigation buttons in the middle. that's a step backwards in my opinion.
Click to expand...
Click to collapse
What exactly is causing the issue with the bootloader?

acdcking12 said:
What exactly is causing the issue with the bootloader?
Click to expand...
Click to collapse
Pixel C was developed as a Chrome OS device, so it has a Chrome OS bootloader. Don't know the implications of that, but apparently it complicates things.

Why should I flash this?
Is there any feature list I missed? Wifi/Touchscreen fixed?

Termynat0r said:
Why should I flash this?
Is there any feature list I missed? Wifi/Touchscreen fixed?
Click to expand...
Click to collapse
Idk what to tell you man. Haven't tried it myself, but usually, the reply is to just flash and see

[KERNEL]Sharkey Kernel for Pixel/Pixel XL

{
"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"
}
This is the new refined home for Despair Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Twitter - http://twitter.com/DespairDev
G+ Community - https://plus.google.com/u/0/communities/117685307734094084120
Downloads:
Basketbuild – https://basketbuild.com/devs/DespairFactor
Google Drive – https://drive.google.com/drive/folders/0Bwcofov-xyI0ZVhQUWJhMm9PMkU
Source:
Github – https://github.com/DespairFactor/
Github – https://github.com/UBERROMS/
Credits:
faux123
franco
Google
flar2
imoseyon
Cl3Kener
neobuddy89
Star Wars
XDA:DevDB Information
[KERNEL]Sharkey Kernel for Pixel/Pixel XL, Kernel for the Google Pixel
Contributors
DespairFactor
Source Code: https://github.com/DespairFactor/marlin
Kernel Special Features:
Version Information
Status: Testing
Created 2016-10-23
Last Updated 2016-10-23

For the time being we must flash using fasboot
Code:
fastboot flash boot_a Sharkey_R1.img

Nice double thread Glad to see the project in development!

zeeBomb said:
Nice double thread Glad to see the project in development!
Click to expand...
Click to collapse
Not sure why it did that to be honest

Will test it asap! Thx for the quick kernel Support!
Sent from my Pixel using XDA-Developers mobile app

running kernel no problems so far... positive impact on battery no performance issues camera voice phone all working perfectly..????

"If your device fails to comply with your standards of what you consider functioning"
I like you.

DespairFactor said:
For the time being we must flash using fasboot
Click to expand...
Click to collapse
I feel like I read somewhere that we needed to wipe after flashing. Just confirming if we do or not. As my understanding goes, start to finish: unlock bootloader, fastboot flash kernel to either A or B (whichever is active), reboot = profit?
Thanks for the quick development already!

Can you explain the benefit of this?

Atemi1337 said:
I feel like I read somewhere that we needed to wipe after flashing. Just confirming if we do or not. As my understanding goes, start to finish: unlock bootloader, fastboot flash kernel to either A or B (whichever is active), reboot = profit?
Thanks for the quick development already!
Click to expand...
Click to collapse
No need to wipe, just unlock bootloader(which will wipe your phone), then fastbot flash kernel and reboot. To change your active partition you can use "fastboot --set-active=a"
Moogagot said:
Can you explain the benefit of this?
Click to expand...
Click to collapse
Uhhhhhhhhhh, it bricks your phone hard

Flashed R5 like a charm on Pixel. Not sure if it matters but I noticed version says it's marlin instead of sailfish. You're probably using the same base and what not though. Figured I'd let you know.

Atemi1337 said:
Flashed R5 like a charm on Pixel. Not sure if it matters but I noticed version says it's marlin instead of sailfish. You're probably using the same base and what not though. Figured I'd let you know.
Click to expand...
Click to collapse
It's literally just one small change in the ramdisk that makes it work, so I just append the Pixel ramdisk to the same kernel. I will remove that when I get anykernel going and it will be the same zip for both devices at that point. Just waiting on TWRP to be public.

I'm looking for a kernel that will circumvent bootloader unlock detect for Android Pay...

DespairFactor said:
It's literally just one small change in the ramdisk that makes it work, so I just append the Pixel ramdisk to the same kernel. I will remove that when I get anykernel going and it will be the same zip for both devices at that point. Just waiting on TWRP to be public.
Click to expand...
Click to collapse
Good to know. Thanks again!

Cares said:
I'm looking for a kernel that will circumvent bootloader unlock detect for Android Pay...
Click to expand...
Click to collapse
This kernel has the patch

Any news about twrp yet?
Sent from my Pixel using XDA-Developers mobile app

blaze9090 said:
Any news about twrp yet?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Nothing I've heard yet. http://androiding.how/google-pixel-xl-twrp-recovery/

DespairFactor said:
Uhhhhhhhhhh, it bricks your phone hard
Click to expand...
Click to collapse
What I'm asking if what are the benefits of switching to this Kernel rather than using the default? I've tried to find documentation and an explanation with no luck.

Moogagot said:
What I'm asking if what are the benefits of switching to this Kernel rather than using the default? I've tried to find documentation and an explanation with no luck.
Click to expand...
Click to collapse
Then don't flash it, I don't need to convince you that it is better

Definitely interested in trying out this kernel. is there a way to backup the stock sailfish kernel(or does anyone have a copy of it?) that would be able to be flashed over to revert the system in the event that there are issues(such as an app failing due to modded kernel)?

【Treble】【PIE】OnePlus 3(T)

Not my work... Just sharing what I came across...
Works great on our device (with bugs, ofcourse)...
https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ
INSTRUCTIONS
Clean Flash
Download the zip of GSI
Extract the system.img
Flash any treble enabled ROM.
Wipe: Dalvik and Cache
Flash the GSI (system image) from recovery
Reboot & Enjoy
Source - https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801

Thanks which one supports to be download
kpmohamedhussain said:
Not my work... Just sharing what I came across...
Works great on our device (with bugs, ofcourse)...
https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ
INSTRUCTIONS
Clean Flash
Download the zip of GSI
Extract the system.img
Flash any treble enabled ROM.
Wipe: Dalvik and Cache
Flash the GSI (system image) from recovery
Reboot & Enjoy
Click to expand...
Click to collapse
I see two folders on the link.
{
"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"
}
Sent from my ONEPLUS A3003 using Tapatalk

Ours is A only...

Camera fix - https://androidfilehost.com/?fid=1322778262904000685
Call fix - Set phone app as primary
Root - Magisk 16.7
Hotspot doesn't work...
Other minor bugs in normal LOS 16 remains as is...

kpmohamedhussain said:
Camera fix - https://androidfilehost.com/?fid=1322778262904000685
Call fix - Set phone app as primary
Root - Magisk 16.7
Hotspot doesn't work...
Other minor bugs in normal LOS 16 remains as is...
Click to expand...
Click to collapse
can you share some screen shots like Settings, about phone , kernel version etc?
and the source portal?

xuser_ said:
can you share some screen shots like Settings, about phone , kernel version etc?
and the source portal?
Click to expand...
Click to collapse
Updated OP with source... Reverted back to normal LOS 16... If possible when time persists today will flash again and get screen shots...

kpmohamedhussain said:
Updated OP with source... Reverted back to normal LOS 16... If possible when time persists today will flash again and get screen shots...
Click to expand...
Click to collapse
Ok, but out of curiosity why not use LOS 16.0 or NOS 9.0???

xuser_ said:
Ok, but out of curiosity why not use LOS 16.0 or NOS 9.0???
Click to expand...
Click to collapse
Thus is just to experience treble, the future for our device...

kpmohamedhussain said:
Thus is just to experience treble, the future for our device...
Click to expand...
Click to collapse
Not really.
First of all, you can't really experience Treble. There's nothing different for the user, it's just for developers to easier port newer Android versions.
Secondly, it's somewhat pointless if it isn't properly implemented by the manufacturer. There's no benefit to port new version "easily" if you hame much more trouble to get Treble in the first place; might as well use those resources to port the ROM "the old way".
And lastly, as long as hardware manufacturers provide new drivers it's better to have it the old way.
Basically, porting Treble to old devices is more or less an experiment and a fun project for devs, not really expected to work flawlessly or take off.
Sent from my OnePlus 3 using Tapatalk

Well if this is mature, it can benefit both parties though IMO
For users, we can finally have an OS for all hardware just like in PC/Laptop enviroment
For devs, more user will use their product (build), mean increase in donation.
Later it would bring forth companies that build a paid/premium ROM. More devs would get a regular payment rather than relying in donations.
The rom can just including the generic driver to make the phone function for later use to install the driver from manufacture.
Manufacture would be forced to release a constant working driver or else get blamed by all parties.
All that later, we can say goodbye to bootloader lock since phone manufacture would just selling a phone, not the OS inside it.

The main issue here is that this thread is not a development thread, just basically a link towards the thread itself. Not sure this is the right place for that