Related
I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
How to Root a Samsung Focus Windows Phone
the_professor. said:
I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
Click to expand...
Click to collapse
First off, I am not the creator of any of the resources listed below. All thanks should go towards: Dark Forces Team, WindowsPhoneHacker, and the many others who created these tools. Be sure to thank everyone whose tool/website/ROM you used by buying them a drink. Also, I am not responsible for any damage/bricking/etc that may occur as you attempt to modify your phone.
To address the the absence of OS version 7.10.7720.68, I would like to note that OS version 7.10.7720.68 is the original Mango update provided by Microsoft. Since then, Microsoft has continually updated the OS with minor tweaks (think: service packs) for Windows Phone. Though Samsung (or AT&T or whoever) has not provided these minor updates OTA, ROM developers for the Samsung Focus can bake them into their ROMs. Thus, any ROM with a version number higher than 7720.68 will contain all of the features you request (and more). More information as to the features added/fixed in the OS updates are given at the following link.
(link 1)windowsphone.com/en-us/how-to/wp7/basics/update-history
Now, the easiest place to start the rooting process is by visiting WindowsPhoneHacker's YouTube channel. There is a tutorial available (see the following link) that walks you through the whole process. I strongly suggest you watch the video several times to get a good idea as to the process required. Be sure to like the YouTube video if you find it helpful (trust me, you will).
(link 2)youtu.be/0dSTahZY4mI
I also suggest reading the more detailed information provide by WindowsPhoneHacker (see link below). The link takes you to the "Jailbreak" portion of the website which gives useful information on how to root and install custom ROMs. Read the source and the referenced sources three times or more before you even think about rooting your device.
(link 3)windowsphonehacker.com/articles/the_complete_guide_to_jailbreaking_windows_phone_7_and_7.5-09-24-11
At this point, you should be ready to root. Give it a shot. Be patient, stay calm, and good luck!
I have an Alcatel OT 4010x, the Android version of OT Fire (I guess). Firefox OS should be able to run on my phone, right? If yes, can I request for a rom to flash in (and steps, if it's different from flashing an android rom)? Or maybe can someone please point me in the right direction? I have look around Firefox wiki page and XDA's Firefox OS page, but, it seems there's only a guide to port Firefox OS to other phones, can't find an OT Fire's rom anywhere.
Firefox OS needs Android ICS or higher
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.
Ron Shinde said:
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.
Click to expand...
Click to collapse
Isn't that like dual-boot or something? How about something like clean install or anything of sorts? Sorry if it's a noobish question, but, I don't really know about flashing a new OS, I only know about flashing roms of Androids.
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one
I doesn't have enougth rigth to post to roms, so will post here.
WARNING! Everything you do, you do at your own peril and risk. I do not bear any responsibility for your faulty devices.
Knox will tick. ROM in alpha and not suitable for every day use.
Installation instructions:
1. Install TWRP
2. Reboot in TWRP (Menu unlock phone - Recovery)
3. Wipe -> Format Data -> write - yes -> Enter
4. adb push <LineageOS> /sdcard
5. adb push <SailfishOS> /sdcard
6. Into TWRP: Install <LineageOS>
7. Into TWRP: Install <SailfishOS>
8. Into TWRP: Install <Audio FIX>
9. Reboot in System
Enjoy!
Sailfish OS Android HAL based on Lineage OS 14.1.
Downloads:
TWRP for herolte
Lineage OS 14.1 for herolte
Sailfish OS 2.1.4.14 for herolte
Sailfish Galaxy S7 audio fix(based on work of painted.man)
Sources:
https://github.com/Driim
Build guide can be found here.
Problems:
1. WLAN worked partially(can't remember network to automatically connect after reboot)
2. Bluetooth not working
3. NFC not working
4. Fingerprint not working (Sailfish problem)
Debug:
In Ubuntu. Connect USB cable. telnet 192.168.2.15 2323 or ssh.
Changelog:
30.03.2018
Update to Sailfish OS 2.1.4.14
GSM calls fix
12.02.2018
Working mobile data and sms.
Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?
CyanogenLover said:
Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?
Click to expand...
Click to collapse
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.
Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store
dylanneve1 said:
Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store
Click to expand...
Click to collapse
I'm focused on hardware support. Android applications did not even look.
lSDriim said:
I'm focused on hardware support. Android applications did not even look.
Click to expand...
Click to collapse
Yeah you're right.
lSDriim said:
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.
Click to expand...
Click to collapse
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!
CyanogenLover said:
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!
Click to expand...
Click to collapse
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
I update release and add new screenshots.
lSDriim said:
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
Click to expand...
Click to collapse
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.
CyanogenLover said:
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.
Click to expand...
Click to collapse
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.
lSDriim said:
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.
Click to expand...
Click to collapse
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.
CyanogenLover said:
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.
Click to expand...
Click to collapse
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enougth to port new device.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.
lSDriim said:
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enough to port new device.
Click to expand...
Click to collapse
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
Click to expand...
Click to collapse
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.
Click to expand...
Click to collapse
Ah, Ubuntu Touch! That was a good venture. Too bad it didn't last. Let me know if it works better as the HAL for your project.
CyanogenLover said:
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
Click to expand...
Click to collapse
Almost all except UI.
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
Click to expand...
Click to collapse
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
lSDriim said:
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
Not the entire logs! Just the ones with the errors that are produced from whatever needs fixing. Some commands that output constant log updates have filters. For instance, one way I diagnose a problem on Android is connect the device to my laptop, run "adb logcat *:E", repeat the action on the device that works improperly, then stop the output (usually CTRL + C) and scan the errors for the ones about my issue. If there is still too much to sift through, I try again, setting more filters. You can learn what filters you can apply by typing " adb logcat -h".
I don't know if adb works with Sailfish, but you might could discover logcat or something similar that will filter logs and output only the relevant information. As for what you just mentioned, I can diagnose issues with many Linux-based programs. I use Ubuntu. :victory:
As for the Wi-Fi not reconnecting; On the s7 atleast (probably more) there's a line in the build.prop "ro.securestorage.support"
Change that to the opposite of what it's on
solution for audio
I found solution for audio problem.
You have to edit /system/etc/audio_policy.conf:
- Delete AUDIO_OUTPUT_FLAG_DEEP_BUFFER flag on primary audio device
- Comment sections tms and playback_record
You also can pass argument config to pulseaudio-modules-droid and set location to your correct config file instead of editing vendor file.
continua el proyecto esta bien bueno 7u7
lSDriim said:
Almost all except UI.
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
plss for s7 edge
Mujeeb64 said:
plss for s7 edge
Click to expand...
Click to collapse
I do not have Galaxy S7 Edge, but someone else can do it.
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Please do it. unfortunately I have bought this device recently a month ago and feels like i have been cheated by HTC!! No proper support no software or security updates and really poor website with no useful data to end user, it seems that the company produced this model and dumped in the market to get our money and forgotten or ignoring users with at least security updates, even the non branded Chinese phones get better support than this brick from HTC. My first HTC phone was windows mobile on 2008 , it was poorly supported and my bad luck again with HTC u play which has the same situation. I will never buy from this company again.
citorva said:
Hello,
HTC having obviously stopped supporting my smartphone in terms of updating android, I want to create a custom ROM to enjoy the benefits of the later versions of android in Mashmallow.
However, HTC provides the source code of the linux kernel used as well as some tools necessary for the proper functioning of the device. In addition, it also provides a guide to compiling android. Unfortunately, this guide seems incomplete or poorly explained. So I would like to get help in compiling an android rom for this device.
Click to expand...
Click to collapse
Have you been sucessfull in building costom rom
if yes share it please