Database Users

[Q] [Request] SailFish For Dell Venue 7 ???

MOD EDIT: Thread closed. Please see this thread for more information.
Just like in topic ...

jakubekw1997 said:
Just like in topic ...
Click to expand...
Click to collapse
There are no ports yet, it has barely been ported to Nexus devices and the N9 where both of them are missing important key features and has not been released to the public (except the N9). So there are no official ports of Sailfish yet. You might see a port for it later when the OS is officially available for Android devices, where it'll be more documented and easier to port for your common developer.

[Q] What *is* Paranoid Android?

Landed here from the "Custom Roms" link on the XDA forums. What exactly is Paranoid Android? Could there be a sticky for users new to it? Perhaps with some reason on why this ROM is awesome, like CM's "Why Mod?" page?
I haven't found any information *about* this ROM on paranoidandroid.co, and I'm not the only one who's confused.

http://forum.xda-developers.com/showthread.php?t=2583582
#stayparanoid

Pirateghost said:
http://forum.xda-developers.com/showthread.php?t=2583582
#stayparanoid
Click to expand...
Click to collapse
Sadly, that's only the change log. No answers to the question in the first post. Anyone? I'm curious too!

djgebel said:
Sadly, that's only the change log. No answers to the question in the first post. Anyone? I'm curious too!
Click to expand...
Click to collapse
The change log thread contains a list of all features. Period. What more do you need? Use this ROM and you will increase inches? Get more women?
#stayparanoid

Summarize what the ROM is about
Pirateghost said:
The change log thread contains a list of all features. Period. What more do you need? Use this ROM and you will increase inches? Get more women?
#stayparanoid
Click to expand...
Click to collapse
Certainly not more snark or irrelevant hashtags; more of an outsider's perspective instead of a core dev's one would help. Keep in mind that the vast majority of the users haven't a clue what Paranoid Android is, and are rather trying to decide on which ROM to flash. They're not going to compare change logs. How could we help them choose Paranoid when it's right for them?
focus of the ROM - is it theming? de-bloating? features? a mix? security, since it's called Paranoid?
features differentiating it from other ROMs (raison d'etre - why was this ROM made when there are so many out there)
device compatibility - what phones has it been tested on?
stability notes - how mature is the ROM?
what works, what doesn't

Irrelevant hash tags?
Just like the blog states,
Paranoid Android is a custom rom focused on open devices. We aim to not simply add to Android but extend it, utilizing the same design philosophies Google uses with AOSP (Android Open Source Project). You won't find a sea of options but a minimalistic user focused approach to Android.
We only support nexus, oppo, and 1+ devices.
Honestly, if a user wants to know what it is, there are dozens of android blogs and videos that have covered it all.
We don't have our website up, simply because of lack of time and manpower. Everything we have included works. We don't break devices.
And if you actually look at the change log thread it covers the features in detail, so your comment about comparing the change log is null
#stayparanoid

My apologies. Its been a rough day. I will post something more coherent after I recover from today's events
#stayparanoid

Actually that changelog thread has detailed descriptions of each feature they added to AOSP.
Not only the version-to-version changes.
Those feature descriptions are detailed. Not big words but rather a what-you-get. Clear and detailed.
I say that is the most usable description about a custom ROM. Thanks for the PA team!
Sent from XT910 running AOSPAL

Pirateghost said:
We only support nexus, oppo, and 1+ devices.
#stayparanoid
Click to expand...
Click to collapse
Not to forget the official unofficial legacy group over on G+ haha ?☺
#LegacyRocks
Sent from my Paranoid Bionic

1+ models supported?
Pirateghost said:
Irrelevant hash tags?
Just like the blog states,
....
We only support nexus, oppo, and 1+ devices.
...
Click to expand...
Click to collapse
1+ Wich models are 1+?
I get a bit confused
http://www.gsmarena.com/htc-phones-45.php
HTC list:
One E8 CDMA
One E8 Dual sim
One M8 CDMA
One M8 For win CDMA
One Remix
Etc...

torsoen said:
1+ Wich models are 1+?
I get a bit confused
http://www.gsmarena.com/htc-phones-45.php
HTC list:
One E8 CDMA
One E8 Dual sim
One M8 CDMA
One M8 For win CDMA
One Remix
Etc...
Click to expand...
Click to collapse
1+ is the brand, the manufacturer, the company. Their first phone is the one plus one. Let's not be dense here.
#stayparanoid

Splitting the Memopads

Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)

Etterbeek said:
Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)
Click to expand...
Click to collapse
I think splitting them into separate forums would help. It is confusing that several different tablets are lumped into the MeMO Pad section here. I think we need a ME572 and a ME176 sub forum. Is it possible that all of the ME17X's could be grouped together? At the very least I would add to the forums rules that posts must identify the Model Number in the title...

Agreed.

Etterbeek said:
Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)
Click to expand...
Click to collapse
muiriddin said:
I think splitting them into separate forums would help. It is confusing that several different tablets are lumped into the MeMO Pad section here. I think we need a ME572 and a ME176 sub forum. Is it possible that all of the ME17X's could be grouped together? At the very least I would add to the forums rules that posts must identify the Model Number in the title...
Click to expand...
Click to collapse
mikemikemikexxx said:
Agreed.
Click to expand...
Click to collapse
Usually we'll do a split when there is an active development section to avoid people flashing the wrong software to the wrong device. We don't have that problem here since the development sections are pretty quiet. However, if you guys think it prudent, we could add two more General sections for ME572 and ME176. I just worry that doing so will add unnecessary clutter (currently people are doing a good job tagging their threads with the tablet model within the title). Thoughts?

My concern is with Asus's asinine naming convention that people will get them mixed up (which they do thinking about it buying accessories). While there isn't much custom ROM flashing going on (yet), there is a lot of stock ROM flashing that happens so that Root can be (re)obtained. I will defer to what you think is best. I was thinking until Asus gets smart and starts numbering them, list them by year?
I think there are more than three 7" Memopad models but at least it could be cleaned up via year.
As far as I can remember there is :
Asus MeMO Pad HD 7 - 2013
Asus MeMO Pad 7 (176C)+(CX) - 2014
Asus MeMO Pad 7 (ME572C) + (CL) -2015

Okay, I understand the reasoning you are putting forth here. It does amaze me however that this device (ME572) is flying so far under the radar. It has a great price/performance ratio that I think is basically unmatched at this point.
Preventing the flashing of the wrong files onto one of these devices would be a good thing. I do wish that Asus would revisit the locked/unlocked decision however the accounting department must believe that returns would go up if they opened up the device...
I can live without a split as long as we all try to clearly tag the model in our thread titles...
svetius said:
Usually we'll do a split when there is an active development section to avoid people flashing the wrong software to the wrong device. We don't have that problem here since the development sections are pretty quiet. However, if you guys think it prudent, we could add two more General sections for ME572 and ME176. I just worry that doing so will add unnecessary clutter (currently people are doing a good job tagging their threads with the tablet model within the title). Thoughts?
Click to expand...
Click to collapse

Trying to get some info because the lolipop update is bugged.
For me it was very confusing till I discovered there was an earlier version with the same name.

Porting Sailfish to Xperia Z3C

Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!

apollus said:
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.

Thundery Steak said:
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Click to expand...
Click to collapse
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!

apollus said:
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
Click to expand...
Click to collapse
I would really try not to do it on OS X. You need a proper Linux distribution to use, seeing as you're going to be following HADK very closely. It's not doable on OS X system and will never be. You require a Linux system to build another Linux system. If you went through HADK multiple times, you would know this.
I see why you think that OSX and Linux are alike, but they're really not, even when they are both UNIX systems. OS X is bastardized UNIX system and doesn't contain the GNU toolchain and the only thing it shares with Linux is the UNIX core.

Thundery Steak said:
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you..
Click to expand...
Click to collapse
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.

mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
mal-, how is your port of sailfish for the xperia pro working out?

mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.

Thundery Steak said:
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Click to expand...
Click to collapse
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
apollus said:
mal-, how is your port of sailfish for the xperia pro working out?
Click to expand...
Click to collapse
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.

mal- said:
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
Click to expand...
Click to collapse
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know...
I'm probably gonna end up putting fedora on this machine and start trying to learn to use linux (to port). Will be taking a UNIX/Linux intro class soon anyway, so that will come handy.
I am really sick and tired of boring old android and I think the effort to get Sailfish is well worth it... Gonna keep checking into freenode to see if people mention the Z3C.
Mal, thanks for your posts.

apollus said:
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know.
Click to expand...
Click to collapse
It depends on the person doing the porting at how early stage they add the information to the wiki page. Some do it very early some wait until it's reasonably usable. Of course it would be nice to have information about all ongoing porting activity.

[Team-Up Request] Is there any interest in a team-up for SM-T595 Development?

Hello everybody,
My name is Jasper de Kroon, and I've been involved in bring-up and support of CyanogenMod/LineageOS on a few devices in the past, namely Galaxy S Plus, Galaxy Y and LG Optimus G and LG G2.
Currently I'm owner of a new Galaxy Tab A 10.5 (2018) [SM-T595], which I found out doesn't have a very active development community for this specific device.
Now I would like to join forces with others who have some experience with android (LineageOS, but also stock android/AOSP)/kernel development.
I'm willing to set-up a Team Github for this device and even create a means of communications between the team members.
Let me know how you feel about it, and if you would like to get involved.
Also if you have some ideas of your own, just ventilate them in this forum topic.
Greetings Jasper

Nice to see you are taking an Initiative. I found a group on telegram. You can also find ppl there working on SM-T595.
https://t.me/smt595

PsychoGame said:
Hello everybody,
My name is Jasper de Kroon, and I've been involved in bring-up and support of CyanogenMod/LineageOS on a few devices in the past, namely Galaxy S Plus, Galaxy Y and LG Optimus G and LG G2.
Currently I'm owner of a new Galaxy Tab A 10.5 (2018) [SM-T595], which I found out doesn't have a very active development community for this specific device.
Now I would like to join forces with others who have some experience with android (LineageOS, but also stock android/AOSP)/kernel development.
I'm willing to set-up a Team Github for this device and even create a means of communications between the team members.
Let me know how you feel about it, and if you would like to get involved.
Also if you have some ideas of your own, just ventilate them in this forum topic.
Greetings Jasper
Click to expand...
Click to collapse
I am up for this dude