Related
My wife's fully stock (4.4.2) N5110 started getting update notifications from Samsung Software Update.
Per the info, it's a 7.61 MB 'device stability and bug fixes' patch that includes security enhancements and StageFright fix.
Is there information on everything installed with this patch?
Will installing this block any future attempts at root / installing a custom ROM? (If she ever lets me; this is solely her device and doesn't care about root/ROMs )
Since this is a wifi only note8 - how vulnerable is it to stagefright if I don't patch? Everything I've read says 'stagefright is more than an MMS vulnerability' but then the details only go into the MMS vuln :|
Thanks in advance and sorry if this has been covered elsewhere - I searched and didn't find anything.
I noticed the update today and decided to install it. It did not take very long to install and the Android version number is still 4.2.2, so it doesn't seem that there is anything major. I have yet to notice any changes, but I haven't used my tablet much today I should note that I am also using the wireless version of the Note 8.0 and I have never rooted this devices.
If I learn anything else I'll post here.
It's too bad that they didn't decide to bump things up to 4.4.4 (could use those Bluetooth fixes that were introduced in 4.4.3) while they were at it.
Anyway, I just noticed that there's a new stock rom posted for the USA variant on Sammobile.com and samsung-updates.com. So this is officially "a thing." Haven't flashed it myself yet and I probably won't; I've moved on to Cyanogenmod 12.1. But it's nice to know that Samsung is still pushing out updates for this thing.
Sent from my GT-N5110 using Tapatalk
Hello, i havent found a similiar thread so...
We bought an Opel Adam Rocks (2014) in which there is the really nice Intellilink System. Its said it will connect with all newer Android phones that installed Android Auto, but when i plug it via USB (tried different cables already) it says "Unknown/unsupported device detected".
My phone: Oppo Find 7 is ROOTED, on latest OmniROM which is of course Android 6.XXX + Android Auto App
My question: is it GENERALLY impossible to connect rooted/Custom ROM phones to it? is there anyone that was successful?
Its not a disaster since we didn't see it as important but it surely would be nice!
Thanks.
majo334 said:
Hello, i havent found a similiar thread so...
We bought an Opel Adam Rocks (2014) in which there is the really nice Intellilink System. Its said it will connect with all newer Android phones that installed Android Auto, but when i plug it via USB (tried different cables already) it says "Unknown/unsupported device detected".
My phone: Oppo Find 7 is ROOTED, on latest OmniROM which is of course Android 6.XXX + Android Auto App
My question: is it GENERALLY impossible to connect rooted/Custom ROM phones to it? is there anyone that was successful?
Its not a disaster since we didn't see it as important but it surely would be nice!
Thanks.
Click to expand...
Click to collapse
I have similar problem at the moment with Huawei Mate 9 and intellilink R4.0 (both new). I am waiting for new firmware and will contact Opel dealer for update.
I have read different forums that different firmware on phone acts different as well as software on head unit sometimes makes problems.
Generally I have read that also some custom roms work and some don´t.
Also there have been several updates for the intellilink systems since 2014. This will cost some € at Opel Dealer. It is not for sure this helps! Maybe it is waste of money.
In this case it is google bringing the disaster... The app brings no information what is going wrong...
i'm thinking about an update for the Intellilink, indeed... and... at least its good to hear that custom ROMs CAN work, so there is still chance. thanks for the info!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Links
LineageOS Builds:
6. 20180708: fix crash in RealVnc app: https://drive.google.com/file/d/1autEPJKDlBhsSFfuvMqsdQm9bGLB9WNm/view?usp=sharing
5. 20180707: gps, IR, drm: https://drive.google.com/file/d/1nB-PiNsB-cF2D7wFHxz4Y-QMkQp_Sz-i/view?usp=sharing
4. 20180706: https://drive.google.com/file/d/1oSVWlUHhwhWui4sAwhUir0Xyk_coKMmO/view?usp=sharing
3. 20180103: ril (calls + mobile data), small fixes: https://drive.google.com/file/d/1vATLmjfSkTNnl8iojOE0dwTc8XyAOY-S/view?usp=sharing
2. 20171231: 15.1 (8.1): https://drive.google.com/file/d/18SWSyNfkqgyr-P5rD2gdyqBCbgAQK4oP/view?usp=sharing
1. 20170929: 15.0 (8.0): https://drive.google.com/file/d/0B-6nm7Jks0W5OHF1T2ttR3Bzbk0/view?usp=sharing
Gapps
https://opengapps.org
Recovery:
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/Lineageos/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
Thanks to davidmueller13 for help with the config and initial run.
@Valera1978: That sounds very interesting. Thank you for your work.
Installed as a test, which went fine. Unfortunate is does not recognize my sim card
I do get the message insert sim card. Removed and reinserted, but still does not see it.
Further testing g to be done.
Ralph
@Valera1978
Hey my friend, really awesome to see you back with such outstanding rom!
Thank you very much for such amazing work!
I have tested this ROM for a few days.
When starting the device it gives a message system process stopped.
Next error I get insert sim, does not look to be recognized yet.
Further I did not get issues, with the basic programs.
Looks promising
Thank you for all the work on this!
Ralph
@Valera1978
Thanks for the releasing Oreo for the P905. It is sad that there is still no new 12" Note tablet on the market that take it's place. Especially because of that we all appreciate your work so we are not forced to abandon the device.
However I sincerly hope that you continue to release 14.1 versions until this rom is out of alpha. I and presumably others use that version as a daily driver. You skipped september security updates, I presume you couldn't find the time, so I hope for an october release. It is sad that android now needs monthly security updates but it seems it's the way things flow these days.
Kind regards,
mnemonic-de
mnemonic-de said:
@Valera1978
Thanks for the releasing Oreo for the P905. It is sad that there is still no new 12" Note tablet on the market that take it's place. Especially because of that we all appreciate your work so we are not forced to abandon the device.
However I sincerly hope that you continue to release 14.1 versions until this rom is out of alpha. I and presumably others use that version as a daily driver. You skipped september security updates, I presume you couldn't find the time, so I hope for an october release. It is sad that android now needs monthly security updates but it seems it's the way things flow these days.
Kind regards,
mnemonic-de
Click to expand...
Click to collapse
I'm sorry, all september worked with a oreo. I do not forget the lineage 14, I did several test builds, and fixed the pressing of the left button with the s-pen (tasks switching). There is yesterday's build - publish it or wait a couple of days and post a september security update?
In any case, I will continue to work with lineage 14, I really do not like consumption in standbye mode, I want to try another kernel. Also, there is still a problem with adjusting the volume during calls.
@Valera1978,
thanks for clarifying that. I think everybody who uses your rom understands that this is a one man show and your time is limited. Regarding publishing, of cause I can't speak for anybody than myself I presume that people would agree to skip the september updates. The october updates are already available and regarding security I think digital, either everything known is patched and you are secure as far as it possible or your are not. I don't think it makes much of a difference if you have more or less vulnerabilites.
One thing that might interest other people in regards of security update is blueborne. I'm curently not sure on which level this must be patched. If it's the driver level than things might get difficult for devices that went out of support. Your last rom 0823 shows vulnerability regarding that bug collection.
Thanks for your continued work on that rom.
Kind regards,
mnemonic-de
Dont know if this is a known bug but after installing this version i have problems playing videos. Both in the facebook app and on websites with integrated video
@Valera1978 are you using the same Lineage 14.1 kernel? The work needs improvements (in the part of the calls mainly) but for an alpha version is very good. Thank you!
Just curious
Is this rom being developed actively or was it more "Proof of concept" right now.
Asking because i have some issues that i could live with for a while, while it is being developed, but as i see no updates i am thinking of going back to 14.1
I don't use sim card therefore wi-fi only. From the remarks it looks like this alpha is working well except for the mobile functionality. I think I will give it a go if the basics of Google calendar and email are working via Wi-Fi.
Early experience :
Issues
- being used wi-fi only
- does not play videos at all. Some apps think they can play videos but don't initiate and stand still at time=0. Others seem to be smarter and give message video can't be played. I tried YouTube, Chrome, VLC, and Plex
- developers rights enabled but missing nifty reboot menu to boot into other options such as recovery. BTW this does work my Los 15 mido phone
- camera not working with any camera app I tried.
The good :
- seems to be faster.
- battery life also seems to be better, although not hugely so
- S-pen is working. Experience in Squid is good which is this tablet's main use
- Oreo's feature set is very nice once you get used to it. Interactive notifications are hard to miss.
- magisk works perfectly.
Could this possibly work for the T900? Being y'all say Wi-Fi works.
For p900 please
Any development for P900
The P900 has a different SoC iirc so you are most likely going to find a version for that in a different thread.
The p900 is officially supported by lineage so you could probably get it directly from the source! Nevermind not released just yet, probably soon though!
I tried the first version, released in September but it was not good because video playback (Facebook, youtube, dailymotion, etc.) was not working.
Has anyone tried the latest version and if you, can you confirm if the video playback works.
I have used this a couple of days now. For the purposes I do use it , all works fine.
Earlier question on video playback, I use vlc and this works.
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.
It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.
Hi,
I built and deployed the latest aosp 11 on this device. The phone is on the t-mobile network in USA.
All went ok but if I put the sim in the first slot, everything works except that the mic works ONLY if I am on speakers, cannot talk normally. Note that if I plug a headset, all works normally, but who can always use a headset?
If I put the sim in the second slot, most works including the mic, but sometimes I do not get messages. This is an issue specially when I need to get some token.
Anybody saw something like this?
Note that if I flush the stock Sony rom, there are no issues.
Thanks,
M.
Just an update, a few days back I rebuild aosp 11 and did a clean flash, exactly the same behavior.
If anyone do see this behavior and have a solution, please post it here.
Best, M
If anyone updated the OS to aosp 12 (or 13) please post your results here. I still have the issue shown in this thread.
Note that all seems ok with the stock android, it is only with the aosp 11 (the one I tried).
Me again and more on the saga of installing aosp on xperia 10 III. Since now I got a new daily driver (pixel 7 on which I installed grapheneos), I was able to test a bit more on 10 |||. I tried installing aosp 12. It worked and it booted, it looked ok. However after a reboot, it no longer sees the slots and the sim cards. I tried booting a few times, the same thing.
What is sad is that this exact behavior was on aosp 11 long time ago but was eventually fixed.
I am really disappointed by the very low quality of the sony aosp. They claim that they support it but when you install the aosp provided by them, it really does not work for the most basic things...
The hope to use this great device is when someone like Lineageos will release a version of their os for 10 3...
Q: what test is really done by Sony when releasing the aosp for a device, when something that simple does not work reliably?
Thanks,
M.
Just to complete my tests, I did install aosp 13 on the device. The installation worked but as with aosp 12, it did not detect any slots or sims. Reinstalled 11 and it does work but with the issues in this thread and another one from me.
I hope that someone from Sony will fix the issues otherwise why even say that they support aosp?
Thanks,
M.