[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.
Why do we have to make long distance calls and send sms to use this app?
http://forum.xda-developers.com/showthread.php?t=1422969
Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.
XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb
Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....
Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?
Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk
xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838
xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.
itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^
srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse
Related
Dear,
Does there exist an application on android where we can set profiles like on windows?
so, On profile 1 (Public) some applications will be not visible, call history and sms messages and whatsapp chats are not viewable, while on the other profile which needs a password, all apps and data are available?
Thanks
Is possible on tabs.
We can create multiple account there.
I don't know about mobile.I use low end mobile,which doesn't have.May be high end device should have.
Sorry if Iam wrong
sanjaykumar.sanjay69 said:
Is possible on tabs.
We can create multiple account there.
I don't know about mobile.I use low end mobile,which doesn't have.May be high end device should have.
Sorry if Iam wrong
Click to expand...
Click to collapse
I think this is related to the android version and not the device.
And for me, i am using latest android version.
hassanayoub85 said:
I think this is related to the android version and not the device.
And for me, i am using latest android version.
Click to expand...
Click to collapse
Yes, you're right. Multiuser support is what you're talking about, and it is available from android version 4.2.2 and above. It is enabled on tablets by default. For phones, you would need to flash custom ROMs that have multiuser support. If you're not on 4.2.2+, then you could try the SwitchMe app on the Playstore instead (requires root).
immortalneo said:
Yes, you're right. Multiuser support is what you're talking about, and it is available from android version 4.2.2 and above. It is enabled on tablets by default. For phones, you would need to flash custom ROMs that have multiuser support. If you're not on 4.2.2+, then you could try the SwitchMe app on the Playstore instead (requires root).
Click to expand...
Click to collapse
Thanks for the app, will try it now, however i prefer to use vustom firmware.
Any stable custom firmware supporting multiusers for samsung galaxy s advance I9070?
Sorry
hassanayoub85 said:
Thanks for the app, will try it now, however i prefer to use vustom firmware.
Any stable custom firmware supporting multiusers for samsung galaxy s advance I9070?
Click to expand...
Click to collapse
Since I do not know much about your device, you should probably ask this question here:
http://forum.xda-developers.com/forumdisplay.php?f=2100
You're bound to get a better answer that way!
P.S. When you ask in that forum, avoid using words like 'best rom' or 'stable rom'.
Modded version of Fitbit Mobile to allow sync on all devices with Bluetooth 4.0 Low Energy.
Minumum Android 4.3 version required!
NB Please read official report Android device compatibility
It's recommended to disable background updates or manually turn on/off Bluetooth when sync needed.
Here are reset device instructions: How do I restart my tracker?
Reported as working on devices:
- Google Nexus 4, 5
- Google Nexus 7
- Galaxy Nexus (some ROMs require additional BTLE libraries)
- Samsung Note 2, Note 3
- Samsung Galaxy S3, S4
- LG Optimus G, G2
- LG optimus 4X HD (starting from 4.4.2 (omni rom tested))
- HTC One
- HTC Evo 4G
- HTC DNA
- Motorola Atrix HD
- Motorola Moto X, Droid Maxx (some 4.2.2 ROMs with BTLE are also compatible)
- Sony Xperia Z, Xperia Z Ultra
- Oppo Find 5
Download Mega | AndroidFileHost
can support sony z ultra? if so,i will buy fitbit flex.
adx_x said:
can support sony z ultra? if so,i will buy fitbit flex.
Click to expand...
Click to collapse
It should support this device - it has Bluetooth 4.0 with LE and you can find Android 4.3 firmwares.
I don't have sony z - so ask people in your device thread to be 100% sure.
dimfish said:
It should support this device - it has Bluetooth 4.0 with LE and you can find Android 4.3 firmwares.
I don't have sony z - so ask people in your device thread to be 100% sure.
Click to expand...
Click to collapse
thanks，i have buy it，tomorrow report if can support z ultra...
Hi,
works perfectly with a rooted Galaxy S4, thank you!
Great, it works on my Nexus 7 running CM!
Not working on my Galaxy Nexus though, running stock. Do I need to switch to Cyanogenmod for proper BTLE support with that device?
JeremyNT said:
Not working on my Galaxy Nexus though, running stock.
Click to expand...
Click to collapse
Please read bold red text in 1 post - Android 4.3 minimum required. Also visit thread for your device with BTLE Drivers.
dimfish said:
Please read bold red text in 1 post - Android 4.3 minimum required. Also visit thread for your device with BTLE Drivers.
Click to expand...
Click to collapse
Well the device is running 4.3, but I guess Google disabled BTLE on the Galaxy Nexus for some reason. BTLE works in CM, and I only recently switched back to stock, so I didn't know it was missing.
The needed modifications to stock GNex are on this thread if anybody else encounters this situation:
http://forum.xda-developers.com/showthread.php?t=2387107
JeremyNT said:
Well the device is running 4.3
Click to expand...
Click to collapse
I see I'm sorry I thought you have 'toro' or 'toroplus' - they don't have stock 4.3 like 'maguro'
dimfish said:
I see I'm sorry I thought you have 'toro' or 'toroplus' - they don't have stock 4.3 like 'maguro'
Click to expand...
Click to collapse
I should have been more specific! Fitbit sync seems to work fine for me now that I have applied the modifications to re-enable BTLE, thank you for posting this apk
Thanks a lot dimfish, it's work for me on my s3 with slimbean 4.3. :good:
Awesome work!
Thanks dimfish, this is fantastic!
What does this mean for BLE functionality with other apps, Endomondo for example? Is this a possibility?
Thank you for this app... Just replaced the one already installed and I can now sync with my phone...
Sent from my SM-N900 with Tapatalk
Since you've made this modification, maybe you'll be able to enlighten me to the situation with 4.3 and Bluetooth Low Energy.
Did google push out the BLE spec in such a way that we theoretically shouldn't have to have a hacked app to sync with BLE devices on any 4.3 device, or is it far more complicated in that each device must be custom tailored in the code of the application to sync properly?
If the former is true, I can't really wrap my head around why the Galaxy S4 GPe 4.3 device would have syncing working perfectly with the stock fitbit app, but not the HTC One running a GPe 4.3 rom.
If the latter is true, google didn't fix anything with regards to BLE.
dimfish said:
Modded version of Fitbit Mobile to allow sync on all devices with Bluetooth 4.0 Low Energy.
Minumum Android 4.3 version required!
NB Please read official report Android device compatibility
It's recommended to disable background updates or manually turn on/off Bluetooth when sync needed.
Here are reset device instructions: How do I restart my tracker?
Reported as working on devices:
- Google Nexus 4
- Google Nexus 7
- Galaxy Nexus (some firmwares require additional BTLE drivers)
- LG G2
- HTC One
- Samsung Note 3
- Samsung Galaxy S3, S4 (custom ROMs)
Click to expand...
Click to collapse
Daman09 said:
Since you've made this modification, maybe you'll be able to enlighten me to the situation with 4.3 and Bluetooth Low Energy.
Click to expand...
Click to collapse
Actually I didn't read Google specs, however I don't see any reason why Fitbit should lie about 48 hours problem described here
So trying to avoid this problem they hardcoded supported devices (so you were able to fool it with modified build.prop).
But lets be realistic - this problem right now affects only Fitbit trackers, while android is still working and bluetooth is working - and when Google decide to help fix this specific problem - who knows...
You sir, are my hero! thanks man
Just tried this on my Sprint HTC Evo 4G LTE running CM10.2 (2013-10-11 nightly). I can confirm that it works perfectly with my Fitbit One! Thanks dimfish!
Working on Motorola Atrix HD
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
A few questions, pardon my n00bness:
-Does my HTC One have to be rooted for this to work?
-Does this modified apk modify my build.prop file?
-If so, does the app reverse this change once uninstalled?
Thanks!
I love you.
Working great on my cm10.2 for sg3
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
CM 11 = CyanogenMod..
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, an enhanced reboot menu, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as wi-fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. CyanogenMod does not contain spyware or bloatware. In many cases, CyanogenMod may increase performance and reliability compared with official firmware releases.
CyanogenMod is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
Source: CyanogenMod Wiki
Click to expand...
Click to collapse
Please tell me how to get a 4.4.2 version. And also please tell how to take a backup of my original firmware if I wish to rollback to original firmware in case
Regards
Sent from my GT-I9082 using XDA Free mobile app
umang2792 said:
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
Click to expand...
Click to collapse
You should better read/ask in your phone's section.
Here is a short preview of the "advanced" android world :
- In order to backup your phone data you need a recovery.
- The most known recoveries are CWM and TWRP (in most phones you get into recovery pressing power and volume buttons while the phone is off).
- From the recoveries you can install a new ROM (firmware) to your phone, make a backup/restore or flash zip files (that run commands and move files)
- Cyanogenmod / Cm is a famous ROM with different versions for many phones. Cm11 is the Cyanogenmod kitkat version (10 jellybean, 9 icecream etc)
I hope you got the main idea
Sorry I am not getting the backup and restore option in my cwm as it shows in the videos
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
jerpelea said:
Now you can build the latest Android with the latest 4.4 kernel
Click to expand...
Click to collapse
Does it also mean that the official firmware from Sony will be updated with this new kernel?
I am not a developer but built it following the guide using the sources since a few months back. Boots and runs. Even used it for a time. But couldn't get fingerprint sensor to work properly. When I used 8.0 branch it was working but very slow and roughly. (Nowhere near the sensitivity of the stock rom) now with 8.1 branch can't get it register fingerprints. Sensor works, starts enrollment and progresses, but at the last step it gives error. However seems like more sensitive and faster than before. Another problem is the battery drain when idle. When using the phone daily routine not that bad, slightly less screen on time compared to stock but the real problem idle battery drain. %15-20 in 6-7 hours. According to battery starts appears to be related to Google play services which is always a serious battery killer for custom roms for years. Other than these did not notice any serious problems. And all this without any changes or tweaks. Straight from the source. Good job Sony imo.
@maluus Don't know if this also applies to compiling roms, but Sony just (march 8) released a new version (v11) of the odm image, which solves fingerprint enrollment issues you seem to describe for the omnirom 8.1 build:
https://developer.sony.com/file/dow...es-for-aosp-oreo-android-8-1-kernel-4-4-loire
Yeah heard of it. I was using v10 oem image last time. When i get back to home I'll try with v11 and will see if fingerprint issue is solved. If it's ok i can use it as daily as it is. If battery drain problem is solved too it will be pretty much everything i expect.
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
battery drain is fixed and new kernel binary will be released today
FM-radio will work someday on kugo in custom roms?
Anyone tried a recent aosp build with v11 binaries yet? Does fingerprint works correctly and accurately? How is the battery life compared to the stock? What is screen on time?
Just installed an AOSP build from March 15th together with v11 binaries and Micro GApps. Fingerprint is working.
And the battery life? I'm home though. I'll be building soon ?
droncheg said:
FM-radio will work someday on kugo in custom roms?
Click to expand...
Click to collapse
for the Open Devices project
in Android 7.x the FM Radio is enabled
in Android 8.x the FM Radio is disabled
Regards
J
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
@jerpelea
Will the Sony Xperia XZ2 be added?
MartinX3 said:
@jerpelea
Will the Sony Xperia XZ2 be added?
Click to expand...
Click to collapse
we are finalizing the last steps before adding it
Regards
J
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
@jerpelea, do you know if there is a modem binary file for this phone that's compatible with T-Mobile VoLTE in the US? The XZ1C has a compatible file (amss_fsg_lilac_tmobile_us_ims_tar.mbn). The stock ROM doesn't, but I'm trying to get VoLTE working and this file would certainly help (if it exists).
Last night I built again. First thing I noticed is how well fingerprint reader works. It's like stock. Congrats to the devs for good job. Camera including video recording and Bluetooth works. But camera seems 1-2 mm smal from sides. Charging issue persists. As Harry pointed 3 amp chargers doesn't work. I tried 2 other chargers. 2.1 amp charger work normally. But 1 amp charger starts do disconnect and connect again after 43-44%. (I'll share the logs with devs) Another problem I noticed is that I can't root with magisk. Tried ver 16, 17 and 18. I can flash from twrp without error but when the device boot up neither Magisk manager is installed nor device is rooted. I did not try with supersu. Another thing to mention is that device boots up pretty slow. Boot crash still happens sporadically.
PS: Supersu works. Sometimes device lags heavily. I noticed especially on chrome and some banking apps.
PS 2: Sharing logs. (Includes 3 amp charging attempt and 2.1 amp charging)
little off, very very basic question, and I could not seem to find the answer.
I understand how to set up a build environment and build an image to the phone, but how about the developer.sony.com latest section binaries?
are they already built images? how will it be different if I build mine following the instructions?
Cheers,
You'll build rom first then you still need to flash that binaries too. They are not alternatives to your home build rom. They are part of the os which you won't be able to homebrew, for your device to work properly.
Hey Guys,
Want to discuss about the latest android developer preview
Will share the findings here.
All are welcome to do it here.
Hope we can create a stable preview soon.
First of all, apps which need to pass a security check don't work in the current build:
- Netflix
- Pokemon Go
- Others?
* The new gesture navigations options can't be found yet under Settings > System > Gestures. Although you can find the 3 options if you search in the settings, you can't change it.
* Some settings can only be changed via the developer options (accent colors, icon shape).
* Signal bar is not visible in the notification bar
Yup.
And fortunately, i am not facing some problems which are mentioned on the Nokia's community page.
Some missing features which i noticed are -
1. Gestures
2.Buggy Download manager
3.VoLTE seems to be working but not completely. I can receive calls but not make calls and send/receive sms.
4.Camera works fine. However, its the vanilla version of Camera app provided by Qualcomm so nothing special expected from it. Nokia will replace that app with it's own in upcoming builds.
5.External storage like SD card is not accessible by third-party apps but only system apps compatible with Android Q . I guess there are some changes with Storage framework because of which apps are not able to access SD card. Checked this with Whatsapp, instagram.
6.Apps requiring Google certifications/safety net or something similar would not work because the OS is still in Development phase.
7.Fingerprint is working fine, but is slow.
8.Dark theme is not properly applied over settings app.
9.Files app crashes when refreshing.
If you are reading this and thinking to update to Android Q Dev Preview. I would like to clarify that the OS is still in development and may get even worse with every update.
So, if you are not ready to use other phone as a backup do not update to Q.
Definitely facing all the above mentioned issues, in addition to Whatsapp being unable to restore backups from Google drive.
Anyways i made the mistake as installing this as my daily driver... Do you guys have any idea if it's possible to rollback even if there's no official support for that?
mariokazzi said:
. Do you guys have any idea if it's possible to rollback even if there's no official support for that?
Click to expand...
Click to collapse
just saw it... "We are currently unable to support rollback to Android 9 Pie. We hope to have manual rollback support available by 16 May 2019. The website will be updated as soon as manual rollback is available." https://www.nokia.com/phones/en_int/developer/
Manual roll
Hey guys just wanted to let you know that Nokia update their dev website with a manual Rollback method
Is this Q DP3, or first build .
Nokia has announced that Q OTA will come in June End with much better hardware ,software optimized
avi_loveindia said:
Is this Q DP3, or first build .
Nokia has announced that Q OTA will come in June End with much better hardware ,software optimized
Click to expand...
Click to collapse
This is preview beta. Very unstable and more for developers. When Q OTA comes your hardware won't change. That's permanent. ?
seedubya said:
This is preview beta. Very unstable and more for developers. When Q OTA comes your hardware won't change. That's permanent.
Click to expand...
Click to collapse
Well, i didn't say hardware change Einstein , I said hardware optimized (better driver, firmware)
avi_loveindia said:
Well, i didn't say hardware change Einstein , I said hardware optimized (better driver, firmware)
Click to expand...
Click to collapse
No need to start name calling mate, I haven't disrespected you and don't intend to. Peace.
Though it's awesome phone on its price sagment, why developers are away to develop custom roms for it ?
deepss1 said:
Though it's awesome phone on its price sagment, why developers are away to develop custom roms for it ?
Click to expand...
Click to collapse
Because Nokia does not allow unlocking of bootloaders?
deepss1 said:
Though it's awesome phone on its price sagment, why developers are away to develop custom roms for it ?
Click to expand...
Click to collapse
Yes I am too waiting for some one to start on custom rom.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
as android app developer. want to start building up rom for our phone Nokia 8.1
not sure no body yet started discussion on this.
Nevermind...
There is any changes in Beta 5 OTA build? Because when I flashed developer preview manually, there was a serious bug, if I touch fingerprint sensor device was stopped working only reboot is option, even if device is just locked and if I touch on fingerprint device stopped working, so I simply rolled back to pie
Recently installed Android 10 OTA build version 00WW_4_070 (directly from pie). I see a working option to unlock the bootloader under the developer options page. Any devs working on rooting and/or a custom rom?
razor17 said:
There is any changes in Beta 5 OTA build? Because when I flashed developer preview manually, there was a serious bug, if I touch fingerprint sensor device was stopped working only reboot is option, even if device is just locked and if I touch on fingerprint device stopped working, so I simply rolled back to pie
Click to expand...
Click to collapse
I installed the ota update (v5) last night. I had faced the same issue regarding the fingerprint sensor after manual install. For the time being, I see that the phone is working well. But when I m receiving calls, I am not able to answer right away. The phone app is freezing or disappearing in the background.