Sailfish OS for Nexus 5
{
"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"
}
MultiROM ≥v28 ability is now in the image (starting alpha2). New to MultiROM? Read here.
This is a community port of Jolla's Sailfish OS for the Nexus 5.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about Sailfish OS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running glibc library.
It only uses parts of Android for hardware enabling (drivers).
Special Thanks to the Nexus 5 porters situ & vgrade, and their helpers: alin, dmt, tbr, iKozzz, MultiROM author Tassadar, Jolla sailors especially jusa, spiiroin, phdeswer, Hannu Mallat, the HADK team, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on Sailfish OS 1.1.9.28
The Nexus 5 port is considered to be of beta quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_hammerhead
HW Support status:
(Look for Nexus 5 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Known issues:
Android app support is not available (unlike in Jolla phone), but you can already play classic Android games like this. On app side there has been some awesome progress on #sailfishos-porters on irc.freenode.net, status reports being on this XDA Thread
All remaining: In Bugzilla
ROM Kernel: Linux 3.4.0
Tips:
MultiROM users: if your primary ROM is Lollipop based, just install any Sailfish OS version accompanied with CM11 .zip, and you'll have best of both worlds working! Thanks to @julle131 for finding this!
Changelog:
Moved to Mer Wiki: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_hammerhead#Changelog.
Created 2014-08-07
Last Updated 2015-10-03
This is really nice, thank you. I do have one question however, since the base is CM 11 M9, would this be compatible with MultiROM?
Edit : Nevermind, downloaded the image and extracted it, it comes with it's own boot image thus answering my question that it does not. Thank you.
TheLastSidekick said:
This is really nice, thank you. I do have one question however, since the base is CM 11 M9, would this be compatible with MultiROM?
Click to expand...
Click to collapse
You're very welcome, our team is non-the-less excited
Considering your question: Please volunteer to make this work under MultiRom et al. However for now you can always boot to underlying CM by doing "fastboot boot boot.img" or permanently flash it to recovery
very excited to see this coming around the corner!!! :laugh::laugh::laugh::laugh:
Sweet. Another new treasure.
Nice job ~
Always, feels good to try something new...
This is another OS like Firefox OS . :silly:
my phone and my printer can run firmware by same group. Fantastic, d/l now
Sent from my Nexus 5 using XDA Premium 4 mobile app
not working for me, am I doing something wrong?
what I did:
1. flashed CM11 M9 then Jolla Image(not working stays on Google Logo, almost waited for 10 min and so then I rebooted phone by pressing power button, still dont work)
then i tried this:
extracted boot.img from cm11 m9 and flashed it via fastboot then flashed flashed jolla image from recovery, still no luck for me...:crying:
Any Help would be appreciated...
EDIT: never mind fixed the issue by flashing via twrp seems like phiz touch was having some issue...
So finally a thread was made in Development.
Here's some more images: http://forum.xda-developers.com/showpost.php?p=53079592&postcount=78
I do hope the thread doesn't get spammed with useless non-contributive posts like "how to flash this", "x doesn't work" or "my phone is brick" like the Sense 6 port.
Lethargy said:
So finally a thread was made in Development.
Here's some more images: http://forum.xda-developers.com/showpost.php?p=53079592&postcount=78
I do hope the thread doesn't get spammed with useless non-contributive posts like "how to flash this", "x doesn't work" or "my phone is brick" like the Sense 6 port.
Click to expand...
Click to collapse
Hi , those images were from an old build, could someone post some images from the alpha1 release yesterday.
vgrade
vgrade said:
Hi , those images were from an old build, could someone post some images from the alpha1 release yesterday.
vgrade
Click to expand...
Click to collapse
Its going to look the same. Its mostly going to be fixes.
This is great, thanks for the link and the heads up. Gonna try this out today.
On a side note: I am really tempted to get the Jolla phone, mainly to run my android apps (plus the OS looks great).
wow, i was looking for this a long time ago
ty
If only this could work with multirom. But im glad this is here
aheeejd said:
During install, or during setting up, there are several roms that ask for su permissions, like roms with lots of features like recents, stuff like that. If you don't give it permission you won't be able to use some features I'm guessing. Grant, always grant
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
my main concern is security. I know if someone wants your info they'll get it but guessing does not put me at ease. thank you for the reply
Sent from my Nexus 5 using XDA Free mobile app
swipe gesture is awesome, but would flash it if apk compatibility fixed xD, thanks sailfish team!
I'm a Jolla user and hope this awesome OS will work fine even in my N5, I've tried the previous build and I'm glad works continue with newer.
Inviato dal mio Nexus 5 utilizzando Tapatalk
This thread is great. Keep it up. :good:
I wait for next
Watching with great anticipation.
Related
{
"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"
}
What is this?
This is the AOKP-android open kang project compiled for the TF201. I have tested this and this flashes with no problem. This rom has waaaaaaaay more features then CM9. Like seriously... it has a option in Settings called Rom Control. You can read about it here: http://forum.aokp.co/
Disclaimer
I or PG are not responsible for what happens to your beautiful prime. So, please act with caution. I am 100% sure this works as I have tested it, however.... if if you dont know how to use adb, i suggest you stop reading right now and learn that first.
BEFORE YOU FLASH PLEASE READ
This rom has been shared for educational and entertainment purposes. Please dont flame, dont complain and please dont wine if you find something that doesn't work, this is why this is Work in Progress. Hopefully, it'll work 100% 1 day, and we of course have no ETA. So please do not ask. Maybe another dev can take a crack at it?
Who made this build? Compiled it?
This build was compiled by PlayfulGod. Please donate to him here: http://bit.ly/yeOD3T. Original work by AOKP. This is just a port for the tf201 and nothing more. Credit to AOKP. I have been given permission by PG to release it to the public. This rom comes with no support. However, you can stop by #asus-transformer on freenode and If i am around... I will gladly help. As the TF201 has been unlocked, i figured it would be beneficial to all android enthusiast to have more than 1 option for roms. That is why we are making this build available. Test it out and tell me what you think. Please expect bugs as this is a WIP. I will post screenshots soon.
What is not working?
Screen Rotation is only in portrait mode (Looking into Orientation Switch on market)
Not all options in the Rom Control work
LED Options
Reboots when pressing the Power Button to sleep the TFP
Screen won't turn off while closing the dock/tablet
MicroSD (Looks like there is a solution for CM9, will look into it)
I have noticed on a few occasions as some of these options are not working with the TF201, it will do a fastboot. So, please do not complain.
Instructions
Install like any other rom, however MAKE SURE you unmount SYSTEM and unmount STAGING.
1. Make sure you're on the latest CWM
2. MAKE A NANDROID
3. unmount system & staging
3. wipe data/factory reset in recovery
4. flash ROM
5. flash Gapps (if you want)
6. reboot
Remember, to make a backup of your current rom. Also make a backup of your boot.img, so if you do decide to go back to your rom you can flash the boot.img and you'll be back to normal.
How to backup your Boot.img? You can use ADB or Terminal Emulator
1. su (to make sure you have #)(if your in adb.... adb shell)
2. dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
Wanna restore to what you had?? Heres how to do it right....
So you saw it, you like it, you can't wait till it completely works, but you wanna go back to what you had for now....
1. Make sure you have your boot.img backed up from the rom your going to restore.
2. Go to CWM and do the Restore
3. Once thats done, go to ADB and flash Boot img
4. adb shell & su (make sure you have #)
5. dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
6. Exit & Reboot
Now you should be back exactly where you are now be4 you flash AOKP.
Download
AOKP for TF201 - Build 26 - http://goo.gl/2LOiO
Gapps - http://goo-inside.me/gapps/gapps-ics-20120224-signed.zip
Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.
redbullcat said:
Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.
Click to expand...
Click to collapse
gapps-ics-20120224-signed.zip
MasterZen88 said:
gapps-ics-20120224-signed.zip
Click to expand...
Click to collapse
Yeah, I found them literally after I said that. Thanks
Yeah baby more roms! Thank you for this, you beat jermain to the punch with aokp but the more the merrier
-EVO-
Woooo! Can't wait to install this thank you!
Yea, i had noticed that also. I completely forgot to mention it. It was 3 am when i posted this last night.
Updated post.
too many choices, need some help
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.
ragesoss said:
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.
Click to expand...
Click to collapse
Kang is not the name of the rom, kang means built from someone elses code Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe as it is "kanged" from source
sent from my Transformer Prime
No NTFS support ?
Hi, Firstly thanks for sharing the ROM. Installed over the Virtuous ROM (.15 v2) to play with and all installed ok, apps restored via TB, etc. but have found that my 32gb microsd card shows up as a Blank SD Card when inserted (I had to create the Removable subfolders first, as per http://forum.xda-developers.com/showpost.php?p=23006383&postcount=2), this read fine before on the stock roms and also on Virtuous. So guessing that the kernel used on this rom doesn't support NTFS ?
Any plans to get NTFS support included as 90% + of the HD films I have are way over 4gb
A feature list for the OP would be nice.
I believe it has the same features as listed on this lsit: https://sites.google.com/site/androidopenkangproject/feature-lsit?
YES!!! AKOP on my prime!! This rocks thank you!
cant wait to flash it!!! thx buddy!
For those that are unaware, AOKP is AWESOME!
I don't think I will flash this until some of those bugs are cleared up, but as soon as those are fixed I am in.
I have not used CM9 yet, but AOKP on my Galaxy Nexus is more stable than any CM7 ROM I ever tried. Its packed with features and the devs are always adding new stuff.
marko! said:
Kang is not the name of the rom, kang means built without permission or stolen work. Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe
sent from my Transformer Prime
Click to expand...
Click to collapse
I must correct you, Kang is an official denomination of self compiled CM from sources. The Kang ROMs are not stolen !!
CM are built by a buildbot automatically every day or nearly, everyone can build a Kang from sources (remember it's open source) and when you do that the build script automatically add 'Kang' to the name of the ROM as it appear is Settings> About Device menu.
Thus you can easily make the difference between ROM compiled by Cyanogen buildbot and ROM compiled by dev. Usually Kangs are a way to pick only interesting commits for the specific device (called cherry picks) or even removing some commits that are eventually causing bugs.
For example on my optimus 2X phone, CM9 is not officially released, but the CyanogenMod dev in charge of maintaining CM tree for our phone made a Kang to enable us to test it (he named it SelfKang with humour ...)
Don't write such things it could lead to misinterpretations...
Hell yeah. Thought I was in the inc2 forums for a second. This is the best ics rom I've ever used (at least for mobile). Can't wait to give it a run on the tfp
Sent from my Incredible 2 using XDA App
"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.
Nice AOKP on my Desire HD and now my prime. This is great news. For everyone who doesnt know, there are a lot of customizations with rom control. Once the few bugs are worked out, its golden.
Sent from my HTC Desire HD using Tapatalk
Thank you sooooo much! The C9 ROM was KILLING ME! Bug city. After flashing it, I couldn't get wi/fi on any of the other ROM's i was using. So far this looks great. I'm hoping the landscape fix is coming soon.
hobbypunk said:
"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.
Click to expand...
Click to collapse
From what I've learned the kernel is usually the issue with orientation. I have a Skyrocket and of I use a kernel from the Hercules (TMobile version) the orientation is opposite. Sometimes in settings you can torn off specific degrees of orientations.
Thanks for the tip about the app BTW.
Sent from my SAMSUNG-SGH-I727 using xda premium
[ROM][3/26/15] Pure AOSP ROM -★| 5.1.0_R3 | LMY47I | Build #6 | Proof of concept! |★-
Pure AOSP for the Nexus 6
Preface:
This is meant to be a Pure AOSP build with just minor edits to stop the stock recovery from replacing custom recovery, add some Google edits to the ROM for GPS, and modify the ramdisk so as not to preclude it from being rooted! Its not meant to be a fancy ROM, its just meant to be a baseline AOSP ROM. This ROM was produced by following the steps in the build guide I wrote. See post #2 for build guide links!
Install Instructions
Must have custom Recovery on unlocked device
Copy ROM to device (Gapps and root too!)
Reboot to recovery
Choose Factory reset (TWRP, not sure what CWM is)
Choose Install ROM
Now you can install the Gapps, and Root if you desire!
Specs and Download Link!
Android Build Version: 5.1.0_R3 / LRX22G
Current Build Date: 3/26/2015
Download: HERE!
Recommended Add-Ons
SuperSU by Chainfire here: SuperSU Stable Version
PA Gapps here: [GAPPS][5.0.x][BETA] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's)
Change Log
1/19/15 - Build 6 - Complete rebuild as proof of concept for 5.1.0_r3. This is PURE AOSP with no edits and no fixes.
1/19/15 - Build 5 - Fixed Youtube, Net flix DRM play back issue. Thanks to @sykopompos for pointing me to @ayysir git hub for the fix by @BeansTown106
1/17/15 - Build 4 - Fixed Browser force close in settings.
12/19/14 - Build 3 - Updated to Android 5.0.2_r1
12/15/14 - Build 2 - Switched back up to block based build for installation speed! Thanks to @hlxanthus for the 411!
12/14/14 - Build 1 - Initial build
{
"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"
}
Click to expand...
Click to collapse
Build Guide Link
Want to build this exact ROM yourself?
Here is a great build guide I wrote: [Guide][1/19/2015] Building AOSP for the Nexus 6!
Change Log
Add-Ons
Sprint Data connectivity linked by @orlzzt is HERE!
Reserved!
Hmm... I'll take this for a spin later. Thanks!
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
hlxanthus said:
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
Click to expand...
Click to collapse
Yes. Its pure AOSP.
Can you give me a calculation of time to install block based and file based ROM? Several times longer is a strong statement. If you could produce factual data I would appreciate.
However I am still not going block based installs because the user can take this ROM, add or remove things before it is even installed.
But I look forward to the numbers you show me! If you dont have the data that is fine. I can change the false to try in the script ota_from_tools and test it myself. Should only take a few minutes to recompile as block based.
But thanks for the input!
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Great to finally see you here scrosler!!! Always great to welcome another knowledgeable developer to the forums
hlxanthus said:
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Click to expand...
Click to collapse
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Ok, I timed the file based intall, it was 2:16.08 (which was closer to your 3 minute estimate but a far cry from the 5 minute estimate)
I will build a block based ROM tonight and test to see the difference. However its still very unlikely I would change the current set up. Although I could just post both! :highfive: Win Win for everyone :good:
But once again! Thanks for your input!
scrosler said:
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Click to expand...
Click to collapse
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
hlxanthus said:
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
Click to expand...
Click to collapse
We are cross posting. I timed it myself and it was just a hare over 2.25 Minutes. Which is not that far off from your assert of 3.0 minutes.
Im going to build the block based tonight and post it so people can have both options.
You brought a valid point. Once again, thanks for your input!
Edit: Also, wasnt trying to beat you up, I just like solid number comparisons.
Haha no worries, us old optimus s veterans need to stick together ?
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
hlxanthus said:
Haha no worries, us old optimus s veterans need to stick together ��
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
Click to expand...
Click to collapse
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
gcng said:
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
Click to expand...
Click to collapse
You just flash a no force encrypted kernel which I basically any of them. And as @scrosler just said he may just build it into the next build.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
And yes, same user name over at android central, I had DanteRom that I released. ?
EDIT:
DAMN! There is no comparison from Block Build and File based build
Block build was roughly 2 minutes and 30'ish seconds
Block based build was 10'ish seconds!
Hey Scott glad you are building for the nexus 6 are you planing on a Clean Rom also? Or just keeping it aosp
scrosler said:
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Click to expand...
Click to collapse
I'd say leave it encrypted for now until faux finally makes it to the threads...from his g+ posts it seems his found a way to keep the device encrypted yet have around the speed as though it was unencrypted. And he's a very open source guy so I'm sure he'll share the magic
Deodexed and Rooted Remix-OS-PC - 64-bit and 32-bit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to Android -x86 Open Source Project and jide.com for offering us a free version of Remix OS/Android OS for PC. Visit jide.com for more info. And for downloading an official UN_rooted version of Remix OS: www.jide.com
Visit jide.com and subscribe to receive official updates on Remix OS for PC.
Disclaimer: I will not be responsible if you screw up with your device.
Note:
- 64-bit UEFI Boot & Legacy BIOS compatible
- 32-bit Legacy BIOS only
How to launch Remix OS for PC
Visit jide.com for more details about installation.
1- Download Remix OS for PC package and then unzip the file.
2- Run the Remix OS USB Tool to burn the .iso file onto your USB flash drive OR you hard drive/hard disk.
3 -Reboot your PC and press 'F12' (PC) or the 'Option' (Mac).
4- Select either "Guest Mode" or "Resident Mode" to start Remix OS for PC.
- Enjoy and don't forget to buy me a beer.
Latest Beta version- 2.0.202-Apr 12th 2016
• Visit jide.com for more info about update. www.jide.com
Change log-Up to Date
- Made from official. iso beta Version: 2.0.202-Apr 12th 2016
- Rooted with latest SuperSU RW-working
- With Busybox
- Deodexed with API-Level 22 [Framework, /system/app & /system/priv-app]
- Zipalign all apk files to optimize Ram usage with latest SDK
- Add AdAway-release_Build-Oct.09.2015 No ad, no malware, no spyware, bloatware
********************************************************
Download-64-bit-2.0.202 April 12th 2016
https://mega.nz/#!NxAH1YaB!B9k7hBqsF2PXdKqiqJ1b5NxXdfjZYHHydybx5rk3MWI
Download-64-bit-2.0.102-Mar 1st 2016
https://mega.nz/#!EppHiIYb!npVQkFMgq44P1b5h01azv2r94pZnAxyxcPNfl0i-y6I
Download-32-bit-2.0.102-Mar 1st 2016
https://mega.nz/#!Rk5nTDAD!aUZSjWS5o8Z7OtDtuZfSUgZOoub2W_84kLt75b_G89k
********************************************************
See the following thread to Install GOOGLE PLAY SERVICES On Remix OS 2.0
********************************************************
To Install GOOGLE PLAY SERVICES On Remix OS
http://forum.xda-developers.com/remix/remix-os/app-install-google-play-services-remix-t3292087
********************************************************
If you like my work, buy me a beer
TO DO
- coming soon
Special thanks to:
Thanks/donate all the devs, jide.com team, Android -x86 Open Source Project, & respect all the devs & enjoy
Chainfire for amazing work SuperSU
SuperR for great work (SuperR's Kitchen)
BSDgeek_Jake for Adblock
And other members and devs
Can you release the "leaked" version? That one is more stable and even has google play store preinstalled. It is even more stable than this official release when it comes to running games and stuff.
Also, would you kindly upload it to somewhere that is not mega. I hate the god damn mother hugging, son of a biscuit website. No support for accelerator support, no nothing. And when I use the browser download mode, it always fails at 580mb or something.
can you zip the img file using ultra commpresion sir??
that file is to big to download using slow connaction
TheBasterd said:
Can you release the "leaked" version? That one is more stable and even has google play store preinstalled. It is even more stable than this official release when it comes to running games and stuff.
Also, would you kindly upload it to somewhere that is not mega. I hate the god damn mother hugging, son of a biscuit website. No support for accelerator support, no nothing. And when I use the browser download mode, it always fails at 580mb or something.
Click to expand...
Click to collapse
I will try to do later tonight. Let me find the leaked version.
Sent from my Nexus 6P
janjan said:
I will try to do later tonight. Let me find the leaked version.
Sent from my Nexus 6P
Click to expand...
Click to collapse
Thanks. The leaked version is very easy to find. Its quite popular after people found out that the official builds had no google play and were also very unstable. Funny, how an older alpha is better than newer alpha.
Also, can you make screen recording work on it? I just cant make it work no matter how hard I try.
Thanks.
Regards
TheBasterd
PS: Keep up the good work.
kretex said:
can you zip the img file using ultra commpresion sir??
that file is to big to download using slow connaction
Click to expand...
Click to collapse
Yes. Properly do that
Sent from my Nexus 6P
Thanks for your work on that
Alpha official and leaked system.img are available for download now. Leaked version has already Google Play services. I will try to upload some where else. I can't upload to my Google Drive. Need some more space.
Sent from my Nexus 6P
TheBasterd said:
Thanks. The leaked version is very easy to find. Its quite popular after people found out that the official builds had no google play and were also very unstable. Funny, how an older alpha is better than newer alpha.
Also, can you make screen recording work on it? I just cant make it work no matter how hard I try.
Thanks.
Regards
TheBasterd
PS: Keep up the good work.
Click to expand...
Click to collapse
Try this. It should works fine.
http://forum.xda-developers.com/showthread.php?t=2422061
Sent from my Nexus 6P
janjan said:
Try this. It should works fine.
http://forum.xda-developers.com/showthread.php?t=2422061
Sent from my Nexus 6P
Click to expand...
Click to collapse
Nope. Failed.
So, I think I can officially confirm that screen recording does not work on any android os based on x86 based kernel.
This runs good on my MicroCenter TW-801 even have touchscreen.
rsktkr1 said:
This runs good on my MicroCenter TW-801 even have touchscreen.
Click to expand...
Click to collapse
Nice to know..Enjoy
Sent from my Nexus 6P
I'm getting some ads that crash certain apps, isn't this suppose to be ad blocked ?
Also, what's with the haters going to hate boot animation??
geop0p3 said:
I'm getting some ads that crash certain apps, isn't this suppose to be ad blocked ?
Also, what's with the haters going to hate boot animation??
Click to expand...
Click to collapse
Lol, you've got root access, change it you don't like it
I know I can change it, I just wanted to know why that boot animation it's just so weird lol.
Also, what about the ads? Everytime I open a browser I get an ad, even with ad away installed. Any ideas?
Not doing that for me. Strange. And yes the bootanim is speshul. One of the first things I changed lol. Thanks @janjan for root lol
booogermonkey said:
Not doing that for me. Strange. And yes the bootanim is speshul. One of the first things I changed lol. Thanks @janjan for root lol
Click to expand...
Click to collapse
Wait, you don't get the ads? I've downloaded the iso from the oficial site. Are you using google play services from xda?
geop0p3 said:
Wait, you don't get the ads? I've downloaded the iso from the oficial site. Are you using google play services from xda?
Click to expand...
Click to collapse
Yup, I sure am. Been using Chrome browser as well as the native browser. No ads
booogermonkey said:
Yup, I sure am. Been using Chrome browser as well as the native browser. No ads
Click to expand...
Click to collapse
hat
For me it happens regardless of the browser, hell even some apps are not working because of that. Like Imagine (instagram app) and even facebook don't work. Any ideas how can I fix it?
No clue. Just been playing with this thing for a couple hours. Haven't tried any real heavy apps yet on it. You've tried clearing caches and stuff I suppose?
Possible Release. I am planning to release a tool called Semi Port Toolkit (for Windows PC's only).
You can follow and even contribute
https://github.com/Nischay-Pro/Semi-Port-Tool
Aim :
To simplify the development process of Porting Roms but assisting in porting. Apply Bug Patches or Custom PORTing options, in-app Build Editing. Basically automate certain tasks.
Targeted Platforms :
Windows (Written in .net 4.5 so no XP Support)
Linux (Possible with Mono 3.6 - Confirmed via Travis CI and Ubuntu Dockers)
Targeted Users :
Basically Developers who Port stuff
Even newbies who want to quickly port a ROM.
Possible Expansion :
Yes, supports multiple ROMS, fixes and even devices.
Infact a user who knows how to fix certain issues in a particular ROM Model (Example CM13 - Sensor Isssue) can quickly generate a small script (There is a tool which allows you to make the fix without even writing a single line of code via a GUI APP)
which then can be given or shared to Developers. A Simple drag drop installs the custom fix script which the developer can integrate.
My question is do you guys want it? Is it worth it? Will you use it?
Support :
I shall support it as long as the developers and the community show interest in the project. I shall also try my best to include more devices but starting of with Lenovo A6000 / Plus -> Since it's my phone
Yup
Yeah, who won't. I would definitely, atleast, try to port a few for our device. But, the big question is, "How successful would this be..??" This wouldn't be a easy task for sure. And, as I expect, there will be a lot of bugs. And by "lot", I mean a "LOT" lot. And, fixing those would be a comparatively tough task.
Also, some of those "geeky-heads" like to do this the old school way. The feel to manually do the porting is a complete different experience and achievement in itself.
But, still I'm definitely gonna give it a try. So, Best of Luck for its future.
sasukay said:
Yeah, who won't. I would definitely, atleast, try to port a few for our device. But, the big question is, "How successful would this be..??" This wouldn't be a easy task for sure. And, as I expect, there will be a lot of bugs. And by "lot", I mean a "LOT" lot. And, fixing those would be a comparatively tough task.
Also, some of those "geeky-heads" like to do this the old school way. The feel to manually do the porting is a complete different experience and achievement in itself.
But, still I'm definitely gonna give it a try. So, Best of Luck for its future.
Click to expand...
Click to collapse
I have ported devices but can you share your knowledge of porting devices. Like what files do you generally look for porting.
Bugs will always be a problem. To simplify the process a log is generated and stored. Which is synced with all developers. This is used to find the sweet spot of PORTing the ROM's. For ex : The minimum number of files to have a basic functional PORT. Something like that.
{
"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"
}
Some images of my work.
Kingg01 said:
Some images of my work.
Click to expand...
Click to collapse
:good: It's a wonderful tool
When it will be available for download :good::good::good:
kabtshino said:
:good: It's a wonderful tool
When it will be available for download :good::good::good:
Click to expand...
Click to collapse
The Beta could be available soon. Right now all it does is port ROM's for Lenovo A6000 Plus. But I still need to make it better. I mean I got a success rate (Without Bootloop) of 60% out of 10 installations. Which is quite good enough.
Now we can port roms for our a6000 ?
wow really nice tools but how about the compatibility for other devices A6000 with 1Gb RAM ? its still can use the same ROM with the A6k+ ?
Sparco21 said:
Now we can port roms for our a6000 ?
Click to expand...
Click to collapse
Remember this tool assists in porting by reducing the number of steps. A bit of manual work is still needed to be done by the porter
mark.dx said:
wow really nice tools but how about the compatibility for other devices A6000 with 1Gb RAM ? its still can use the same ROM with the A6k+ ?
Click to expand...
Click to collapse
It should work. That depends on the Base and Port ROMs.
When will share download link and instructions how to port rom ? and from what phones we can port roms ?
Sparco21 said:
When will share download link and instructions how to port rom ? and from what phones we can port roms ?
Click to expand...
Click to collapse
If you are interested in testing it. You may use the compiled sources found in the Debug folder of Github. For now it can port Lenovo A6000 (Plus). It's recommended to port from same chipsets. (Easiest) but it supports porting from rest of the phones also.
Instructions shall be posted soon after a Pre-Beta is released for Closed Beta Testing.
Kingg01 said:
The Beta could be available soon. Right now all it does is port ROM's for Lenovo A6000 Plus. But I still need to make it better. I mean I got a success rate (Without Bootloop) of 60% out of 10 installations. Which is quite good enough.
Click to expand...
Click to collapse
60% success rate is good enough for me. Great work ?
Sent from my Lenovo A6000 using XDA-Developers mobile app
mshoaib7 said:
60% success rate is good enough for me. Great work ?
Sent from my Lenovo A6000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I just need talented PORT'ers to share their methods of porting to newbie PORT'ers.
Also for those people who frequently update their ROMS (Your RR ROM) I provide with a special tool to generate incremental patches for the ROM (Instead of flashing the entire ROM) and also allows you to configure your own methodology of porting.
Lets say you generally copy ABC and DEF Folders from BASE to PORT. You can write a configuration file to automate it in such a way that this tool can read the configuration file and auto port it. Thus repetitive tasks are reduced considerably. If you don't like writing scripts there is a GUI which helps you write the configuration files without you writing a single line of code.
Say hello to Plugins and Tools. Now you can install plugins.
@Kingg01 Hell yeah! Bring it on. You've got some great work man, I'm definitely going to try it. I've ported some ROMs for my Samsung Galaxy Grand Prime which is with the same chipset as A6000 nd most of the things are same. The problem comes with the bugs but this tool might help in that.
Btw I own both phones.
Anyone, please try to ported VIBE UI 3.0 or 3.5 for a6000 ?
Please post your successsfull root, (Magisk) & Any successfull custom recoveries and or custom ROM's fully running on Google pixel 6 devices. Leggo developers!
The question is, why would you want a bloated rom with this great un-bloated device?
Pixels now days come with the best software available.
If you want to customize and root, use Magisk and custom themes.
Hopefully some developers will get these phones in their hands and start working on new ROMs, that's mainly what I'm waiting for to really start enjoying my P6 as well. A big one for me is to de-google the phone and go Lineage/Calyx/Graphene OS.
vandyman said:
The question is, why would you want a bloated rom with this great un-bloated device?
Pixels now days come with the best software available.
If you want to customize and root, use Magisk and custom themes.
Click to expand...
Click to collapse
If by un-bloated you mean lacking any useful options then sure. But personally I want more options, like the ability to assign custom actions to navbar buttons, to hide the statusbar clock without leaving a huge empty space behind, to have PROPER accent colors I can define via HEX code and many many more.
On the other hand an UNbloated device shouldn't come with Gmail, Youtube Music, Google TV, Tags or any other crap preinstalled either, most of which I can't uninstall but only disable.
I can't wait to see what devs unlock with new kernels
Might take a while since Tensor is an unknown, but this would be a great device for Lineage.
LLStarks said:
Might take a while since Tensor is an unknown, but this would be a great device for Lineage.
Click to expand...
Click to collapse
That's alright I expect to wait awhile. I'm excited either way
vandyman said:
The question is, why would you want a bloated rom with this great un-bloated device?
Pixels now days come with the best software available.
If you want to customize and root, use Magisk and custom themes.
Click to expand...
Click to collapse
"great un-bloated device"? Maybe as compared to adding even more bloat from the vendor and carrier, but these are VERY VERY far from bloated. They're disgustingly bloated. More g-spyware than anything I've ever seen.
So why would you want an **UN**-bloated build of AOSP? To get rid of the steaming truckload of dogsh**.
96carboard said:
"great un-bloated device"? Maybe as compared to adding even more bloat from the vendor and carrier, but these are VERY VERY far from bloated. They're disgustingly bloated. More g-spyware than anything I've ever seen.
So why would you want an **UN**-bloated build of AOSP? To get rid of the steaming truckload of dogsh**.
Click to expand...
Click to collapse
You can uninstall or freeze any app you want to. Easy peazy.
I just like having a clean OS with a few minor mods. Oh!, custom kernels are also helpful.
I guess you can call it OCD, after cleaning up people's PCs from all the crap that they installed with no clue on what it really does.
Some people just like installing crap on there phone for what...
Than they go from thread to thread to cry and ask for help because their device has problems.
vandyman said:
You can uninstall or freeze any app you want to. Easy peazy.
I just like having a clean OS with a few minor mods. Oh!, custom kernels are also helpful.
I guess you can call it OCD, after cleaning up people's PCs from all the crap that they installed with no clue on what it really does.
Some people just like installing crap on there phone for what...
Than they go from thread to thread to cry and ask for help because their device has problems.
Click to expand...
Click to collapse
No, you actually can't. Go ahead and try to disable play services and see where that gets you.
96carboard said:
No, you actually can't. Go ahead and try to disable play services and see where that gets you.
Click to expand...
Click to collapse
Google play is whole, different topic in its own.
Some people need it for different reasons than others.
Just like some people need Facebook Twitter, etc. For there life to continue on.
I do not need that kind of bloat ware in my life.
96carboard said:
No, you actually can't. Go ahead and try to disable play services and see where that gets you.
Click to expand...
Click to collapse
I've been using Android devices without Google Play Services by following this excellent guide on all my devices. I'm waiting for my Pixel 6 and will have a go. Not sure if it will work on Android 12, but will have go. In any case I'll be using Xprivacy Lua & AFwall+ for additional privacy.
[GUIDE] microG - Deodex - Signature Spoofing - Debloat Gapps!
microG I am no longer working on this, or updating any information here! This was created back in the day of Oreo. I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T. /e/OS...
forum.xda-developers.com
{
"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"
}
If you follow the aosp build guide you can build aosp pure for pixel 6 ...
Im currently trying to build a custom recovery for pixel 6 before i release pure aosp or any other aosp build.
If your wonder why the kernel says september its because i was using it for magisk root.
Please lmk if find a creation build that's successful for recovery please thanks and good luck to you mate. Enjoy your P6!
allenjthomsen said:
View attachment 5451057
If you follow the aosp build guide you can build aosp pure for pixel 6 ...
Im currently trying to build a custom recovery for pixel 6 before i release pure aosp or any other aosp build.
If your wonder why the kernel says september its because i was using it for magisk root.
Click to expand...
Click to collapse
Yes please keep us updated
With the latest update to the 37 firmware i currently have not been able to get a booting build working without gapps or gapps .
I get a build that boots but it reboots at random for both builds i am currently working to fix the issue and once i do i will be releasing both.
Shannonims restart loop? Set selinux permissive for now if you haven't already.
Proton AOSP early release
Just got my Pixel 6 today, can't wait for GrapheneOS been using it on my Pixel 4a forever. Looks like Pixel 6 support is underway.
gapps version is finally booting and i know why this error is there i need to swap from the current gapps im using to another one but i am closer to non bootlooping builds now since i fixed my issue in my source . i will have a non gapps version coming out sooner for those that dont want to use gapps it will not have spoofing at first i will add that later on.