Hi all,
I've just flashed my Motorola Milestone 2 with the ROM below:
http://forum.xda-developers.com/showthread.php?t=1169038
It previously ran the stock 2.3.4 which was pushed out by Motorola late last year. I rooted the device using SuperOneClickv2.3.1 and then rebooted via Droid 2 Bootstrapper and followed the instructions in that post to install the ROM. The device now boots into MS2Ginger 3.0 successfully and all functions work - except the camera.
Unlike other posts on the forum I can use the hardware button to enter the camera. But there is no image preview on either the camera nor video modes. However, if I "take" a picture, the picture is taken successfully and stored to my SD card. It's as if the preview is just not appearing, but the camera is actually functioning. My symptoms are the same as the poster below:
http://forum.xda-developers.com/showthread.php?t=1515840&highlight=camera+preview
To this end I am a bit lost. Any help or pointers would be gratefully received!
I'm having the same problem.
New Milestone 2 updated to UK 2.3.4 SBF then installed MS2Ginger 3 according to instructions in aforementioned thread (I think I followed pretty closely).
I cannot:
- Play video in Youtube app or Flash (not tried anything else)
- See any preview in the camera app.
Both just display black where the video would be.
Would love to post in developer forum and help them fix this bug (and help sort my own issue too!) but for silly 10 post rule.
I've reposted over in the MS2Gingerbread thread. Hopefully someone will see it and pick up on our problem..
Thanks!
Have you made any progress with it yourself?
I think I'll move on to a different ROM soon as it's a show-stopper. It's unfortunate because I was loving everything else about this one.
I had many problems with MS2Ginger 3 too, even after two full wipes and re-installing, it was still unstable, so I gave up: got back to retail 2.3.6 and now I'm on tezet cm9 and will soon update to this one
Now I got so much used to the ICS interface that I can't go back to GB
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!
It was two months ago when I bought my nexus, my first impressions was cheerful,but,as soon as it started a notification of system update to 4.2.1 showed up and hence my problems started,,,LAG,LAG,LAG, and crazy screen acts,I couldn't even complete writing a web address or read a page of a book,
Not alot of joy with updated stock even after a second upgrade to 4.2.2,,so I rooted added some extra utilities(seeder,lagfix) with no extra improvement,,,I falshed so many custom roms all were 4.2.2,,,,I changed so many kernels,,,,LAG HAS ALWAYS BEEN THERE
I suspected hardware problem,but I noticed the repetition of the complains in forums after 4.2,,,,,,,and the character of the LAG and screen flickers were not reproducible nor consistent with any specific hardware usage
so I decided to give 4.1 a try,and that was it,,,I got the image flashed it rooted added my apps,failed to disable update notification(I can live with that),,,,,,,instaeeld my apps and really just started to enjoy my ---now beloved----nexus
Rooting was a breeze with wugfresh toolkit
flashing was fun with jromflasher on linux
I learned alot aout ADB and Fastboot
and really tried lots of apps and roms
My nexus is back to mind and I'm proud of it
I thought about it this last weekend and I think I'll back to paranoid 2.54 which is the latest 4.1 build.
This is not Original Development is it?
General Section please!
This is wrong section to post a thread like that
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
Hi everyone,
First of all, we want to extend a huge thank you to all of you who have been participating in our beta program. It's been a huge success. By sending in your feedback, bug reports, and general thoughts, you've made OxygenOS even better, and we're making improvements faster than ever before. Today, we have a particularly exciting announcement: Open Beta 3– built on Android Nougat 7.1.1 - is available now for the OnePlus 3T. (Note: Link to the OnePlus 3 post*here)
Key updates in this build:
Upgraded to Android 7.1.1
New Shot on OnePlus wallpaper option
Gallery Improvements
New photo editor with watermark and photo straightening options
Newly added media will be highlighted in Photos section
Image location will be displayed on grid view
Media can be grouped by month and year
Folders and individual media can be hidden
General bug fixes
Known Issues and Fixes
Android pay not able to work on London TFL/Tube
This can be resolved by updating the app via Play store
Compatability issues with certain third party apps
Please visit the download page here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_3/
If you’ve already flashed a previous Open Beta build, you will receive this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data may transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the Open Beta, you’ll continue getting Open Beta OTAs.
Please follow the link below for the UI/UX experience survey. We’d really appreciate a few minutes of your time, as it will help us make OxygenOS even better. One last thing: this is a limited program, so we may disable this download link once we receive enough feedback.
- Feedback on UI/UX:*https://goo.gl/forms/rj3OMW2eywKGoNfI2
Note: If you flash this Open Beta build, you’ll receive Open Beta OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here:*https://forums.oneplus.net/feedback/.
Thank you for helping us build a better OxygenOS.
Never settle.
*
All info taken form offical oneplus page
Sent from my ONEPLUS A3003 using Tapatalk
Quick question, why do we need 3 threads for this?
Thread closed, To keep it simple and easy for everyone please use this main thread:
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240