Related
Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
We're releasing Android 4.1.2 to AOSP today, which is a minor update
on top of 4.1.1.
As a note to maintainers of community builds running on Nexus 7: please update to 4.1.2 at the first opportunity. Future variants of the grouper hardware will have a minor change in one of the components (the power management chip) that will not be compatible with 4.1.1.
The build number is JZO54K, and the tag is android-4.1.2_r1.
Enjoy,
Conley and JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Update #1: 4.1.2 has already started rolling out to the Nexus 7, though mine doesn't see it yet.
Update #2: Since I mentioned seeing 4.1.2 with this very build number in the server logs, I'll throw in the devices that I saw running it, in addition to the Nexus 7 (this doesn't mean the updates for them are out now, but rather a good indication of what's to come):
Are we ready?
JellyBean 4.1.2, the incremental follow up to 4.1.1 isn’t a major update by any means, but promises to improve performance, increase stability and fix certain bugs.
It also adds rotation ability to the homescreen, something that wasn’t possible in the previous version of the software.
Could someone please post a dump of this (or point me towards the easiest way to download it while running a custom ROM on my N7)? I'd like to hack away at pulling out the launcher and making an update.zip for it.
Hi everyone, I hope this update will fix the lag problem with few mb/gb free on my N7.
I dont want to flash the factory image cause it wipes everything.
If I flash a nexus 7 stock rooted odexed will I receive the update? What do u suggest?
Hopefully Google fixed the bad display calibration!
http://tinyurl.com/8ouzlks
dragpyre said:
Android police just announced that a 4.1.2 update has been released to AOSP, and the Nexus 7 is apparently already receiving it!
Are we ready?
Click to expand...
Click to collapse
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.
So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app
rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now, I will soon I'm sure,
JBQ also said that the updated factory images will be available as soon as the OTA is, and that the change can be pulled from the commits in the repository..
That's all for now.
Click to expand...
Click to collapse
No OTA is available now!
rootusr said:
To be clear, What JBQ says in that post is that the source of 4.1.2 will be pushed today to the AOSP repo, he asks to the community maintainers of nexus 7 builds (such as CyanogenMod) to update the source ASAP. it does not mean that the Nexus 7 is receiving an OTA update now
Click to expand...
Click to collapse
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.
ezegm said:
So I have my Nexus 7 rooted and unlocked running stock software, will I be fine to get the OTA?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think you will get the update-notification at least..
The question is if a custom-recovery prevents updating.
edit: xda-user dalew729 says he uses CWM and updated OTA without problems....
rockvoid said:
No OTA is available now!
Click to expand...
Click to collapse
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.
dragpyre said:
Unfortunately, because I'm new i can't post links. If you check the other 4.1.2 thread, and follow the Android Police link, you'll see screenshots detailing this.
Click to expand...
Click to collapse
sorry i wanted to post "no, OTA is available now!"
rockvoid said:
sorry i wanted to post "no, OTA is available now!"
Click to expand...
Click to collapse
I'm going from Glazed JellyBean back to stock for this! XD
bozzykid said:
Actually, there are many reports of Nexus 7 users getting the update so it is rolling out now. It also adds home screen rotation to the stock launcher.
Click to expand...
Click to collapse
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.
Saw the 4.1.2 being reported on twitter. Has me all tingly, curious to see what else is included besides home screen rotation. Currently running Codename android rom so I have to wait. :fingers-crossed:
rootusr said:
Yeap, that is what Im Looking now, no word about that from JBQ but there are those reports, No update for me yet.
Click to expand...
Click to collapse
JBQ has nothing to do with the OTAs so he will not be announcing it.
I really can't wait to try this update out!
Unfortunately, I'm not getting any OTA updates. D:
http://forum.xda-developers.com/showthread.php?t=1928731
Beaten by 2 minutes.
Closed
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
Making headlines today is the news about QuadRooter vulnerabilities in a large number of Android devices (estimated 900 million). I started this thread to allow people to report which current ROMs are showing up as vulnerable using Quadroot Scanner, and which aren't.
Running stock KitKat ROM (4.4.2) on my i9192, I can confirm it suffers from all 4 vulnerabilities (no surprise).
kentchristopher said:
Making headlines today is the news about QuadRooter vulnerabilities in a large number of Android devices (estimated 900 million). I started this thread to allow people to report which current ROMs are showing up as vulnerable using Quadroot Scanner, and which aren't.
Running stock KitKat ROM (4.4.2) on my i9192, I can confirm it suffers from all 4 vulnerabilities (no surprise).
Click to expand...
Click to collapse
take a look here in the second post
http://forum.xda-developers.com/gal...ite-4-4-4-919x-stock-rom-dark-t3403598/page16
AICP MM 21/07/2016. Same, no surprises
Security patch 06/05/2016
RR Remix 5.7.2 R52 i9192
CVE-2016-2059
CVE-2016-2504
CVE-2016-5340
I am evil
Sent from my Samsung Galaxy S7 using XDA Labs
SilviuMik said:
I am evil
Sent from my Samsung Galaxy S7 using XDA Labs
Click to expand...
Click to collapse
SilvioMik has posted the above screenshots from his Galaxy S7 and I think we're all supposed to find it funny.
kentchristopher said:
SilvioMik has posted the above screenshots from his Galaxy S7 and I think we're all supposed to find it funny.
Click to expand...
Click to collapse
Indeed
On some sites they said about the exploit that it affects S7 too. As u noticed it does not
Sent from my Samsung Galaxy S7 using XDA Labs
SilviuMik said:
Indeed
On some sites they said about the exploit that it affects S7 too. As u noticed it does not
Sent from my Samsung Galaxy S7 using XDA Labs
Click to expand...
Click to collapse
That's great... but this is the Galaxy S4 Mini forum, as I'm pretty sure you're aware. So if you want to test and report on that retired S4 Mini you mention in your sig, we can get back on topic.
SilviuMik said:
Indeed
On some sites they said about the exploit that it affects S7 too. As u noticed it does not
Sent from my Samsung Galaxy S7 using XDA Labs
Click to expand...
Click to collapse
How about posting the same for the S7 running CM 13???? LOL
I9195, CM13 20160806 (August 5 patch)
I9195 with CM 11, 4 vulnerabilities. Already knew that KK has so many holes that should make a porno
None on my old nexus 7 with AOKP 4.3 but i9195 with cm13 01/08 nightly has 2
AOKP with Aug 05 security patch
hearkenoath said:
I9195 with CM 11, 4 vulnerabilities. Already knew that KK has so many holes that should make a porno
Click to expand...
Click to collapse
CM11 for 9192 is updated to July patches
RESURRECTION-REMIX v5.7.2
[/url]"]http://www3.0zz0.com/2016/08/10/19/116640700.png[/IMG]
TrustLook just updated their scanner so now it gives the same result as CheckPoint
They have added a GPU scan because "since many QuadRooter issues are activated through Qualcomm's GPU driver" ....... You don't say :laugh:
l'm on CM13, 0809 build,
Updated to latest CM13 nightly 0816.
Now CheckPoint have updated their app also, result is now reversed with Check Point giving a pass, however it's not checking for 2 CVE's now. While Trust Look now fails 5340
IronRoo said:
Updated to latest CM13 nightly 0816.
Now CheckPoint have updated their app also, result is now reversed with Check Point giving a pass, however it's not checking for 2 CVE's now. While Trust Look now fails 5340
Click to expand...
Click to collapse
I believe there is a reason for that, scans for those two are inaccurate. Patches for both these were implemented a while back, yet they got reported as vulnerabilities.
csendre said:
I believe there is a reason for that, scans for those two are inaccurate. Patches for both these were implemented a while back, yet they got reported as vulnerabilities.
Click to expand...
Click to collapse
Yes, you are correct, I believe. And that 5340 exploit one has been blocked by latest updates, so should not show as vulnerable in Trustlook.
Though I did come to the conclusion that at least one bug was not yet fixed properly as it's in the Qualcom OEM blobs, but our phones are safe as Googles inbuilt security checks will prevent exploit working.
Do you guys agree?
Yep, correct. Anyway I am never scared of exploits where you actually have to agree to run an apk, even if it does not require special permission. These are educational, will teach people proper computer use
First of all, I'm not responsible for any damage to your device.
I've extracted v385 drivers from Syberia OS and I'm using it with SuperiorOS without any problems so far. Performance and battery increase are notable even after the V331 update.
This should work for Snapdragon 625, but you can try with other phones following this instructions, but only if their use adreno 5xx gpu.
You can check your OpenGL version with AIDA64 on Display and you can also check your Vulkan version with Hardware CapsViewer for Vulkan.
Added lastest android Q drivers (v415). It was tested on SuperiorOS and AICP but should work with other Pie roms.
Working on Android 9.0 Pie.
OpenGL V385
OpenGL V415
Optional. Flash it if you face a black screen with vulkan apps.
Vulkan 1.0.66
Instructions:
Wipe dalvik, system, vendor, data and cache.
Flash lastest firmware
Flash your rom
Mount system and vendor (not needed for v415)
Flash the drivers
and then flash your other addons.
You can dirty flash vulkan drivers.
Thanks to:
heindrix and his topic
Syberia OS
NATO66613
GiaSen
ThatisJigen
LoveSick55 said:
First of all, I'm not responsible for any damage to your device.
I've extracted this drivers from Syberia OS and I'm using it with SuperiorOS without any problems so far. Performance and battery increase are notable even after the [email protected] update.
This should work for Snapdragon 625, but you can try with other phones following this instructions, but only if their use adreno 5xx gpu.
You can check your OpenGL version with AIDA64 on Display and you can also check your Vulkan version with Hardware CapsViewer for Vulkan.
This zip will also upgrade vulkan to 1.1.87 version.
Download
Instructions:
Wipe dalvik, system, vendor, data and cache.
Flash lastest firmware
Flash your rom
Mount system and vendor
Flash the drivers
and then flash your other addons.
Thanks to:
heindrix and his topic
Syberia OS
Click to expand...
Click to collapse
is it for mm2?
What does this specifically do?
[email protected] said:
is it for mm2?
Click to expand...
Click to collapse
Yes, I'm using it on Mi Max 2 with SuperiorOS.
Does it works with Oreo and nougat also ROMs and miui ROMs?
fgaurano said:
What does this specifically do?
Click to expand...
Click to collapse
It's a newer version of gpu drivers for MiMax2
hakuizanami said:
Does it works with Oreo and nougat also ROMs and miui ROMs?
Click to expand...
Click to collapse
You can try on oreo but I don't think it will work. This version works on Pie and OpenGL V313 works on Oreo.
heindrix's topic had v313 drivers, but the link is off right now. I can try to get them, are you looking for it?
can this be flashed with being tejas driver?
Nope either flash this or mine
vadistar said:
can this be flashed with being tejas driver?
Click to expand...
Click to collapse
It's your choice.. v5 of mine have same drivers..
vadistar said:
can this be flashed with being tejas driver?
Click to expand...
Click to collapse
It's the same thing, but his driver was outdated (v331). I've extracted a newer version and posted here (v385) and the performance and battery increase is notable better over the v331 version. But today he has updated his drivers, so now both should be on the same version.
I also felt in need to link and give the thanks for the original op (heindrix), but somehow my comments wasn't appearing on beingtejas topic.
I already updated it 7 days back,
LoveSick55 said:
It's the same thing, but his driver was outdated (v331). I've extracted a newer version and posted here (v385) and the performance and battery increase is notable better over the v331 version. But today he has updated his drivers, so now both should be on the same version.
I also felt in need to link and give the thanks for the original op (heindrix), but somehow my comments wasn't appearing on beingtejas topic.
Click to expand...
Click to collapse
But since am not home and busy in my work , it's pending , since i not post anything without testing , and am using k20 pro at present..
I updated my k20 pro drivers too and with that i updated max 2, but you posted it just before me..what ever your source is now.. it was not working that time when i first included my drivers with hardrock bro's rom.
Hardrock know better about all those things we did that time to make the best we can give.. let it be.. since i was looking to stop my work for max 2 for long time now i got the reason..
I still add one thing i don't used anything from your sources , even i asked him to help but he didn't answered.. it all by me and it will be..
beingtejas said:
But since am not home and busy in my work , it's pending , since i not post anything without testing , and am using k20 pro at present..
I updated my k20 pro drivers too and with that i updated max 2, but you posted it just before me..what ever your source is now.. it was not working that time when i first included my drivers with hardrock bro's rom.
Hardrock know better about all those things we did that time to make the best we can give.. let it be.. since i was looking to stop my work for max 2 for long time now i got the reason..
I still add one thing i don't used anything from your sources , even i asked him to help but he didn't answered.. it all by me and it will be..
Click to expand...
Click to collapse
The drivers from heindrix's topic was working perfectly as many people with many devices said so and I've tested it too. I saw you there and your comment that v331 wasn't working but his v313 version worked, then you made a topic sharing v313. I posted not only on heindrix's topic but also in yours that v331 was working and the instructions to make it work, but for a reason my comment didn't appear (neither you reply for that comment) on your topic and a very few time later you updated your drivers to v331. Now I've extracted v385 drivers and one day later you update your drivers to v385.
I felt in need to give heindrix his proper thanks. It's done now and people also got v385 that feels way better.
May be you are unable to read properly what I wrote there..
LoveSick55 said:
The drivers from heindrix's topic was working perfectly as many people with many devices said so and I've tested it too. I saw you there and your comment that v331 wasn't working but his v313 version worked, then you made a topic sharing v313. I posted not only on heindrix's topic but also in yours that v331 was working and the instructions to make it work, but for a reason my comment didn't appear (neither you reply for that comment) on your topic and a very few time later you updated your drivers to v331. Now I've extracted v385 drivers and one day later you update your drivers to v385.
I felt in need to give heindrix his proper thanks. It's done now and people also got v385 that feels way better.
Click to expand...
Click to collapse
By the way let it be.. what I did is known to everyone even to the Dev who made this all possible , even I don't even want to waste my time here.. arguing on useless talks.. lol.
beingtejas said:
By the way let it be.. what I did is known to everyone even to the Dev who made this all possible , even I don't even want to waste my time here.. arguing on useless talks.. lol.
Click to expand...
Click to collapse
if you dont mind me asking, where did you compile drivers foem? like the source? i use to think every driver came from same source
I've installed BeingTejas drivers and Kernel V5 combined ZIP file before this thread was created. Can I dirty flash this video driver over my existing one?
I installed it and it boot to black screen, how to uninstall it please
---------- Post added at 07:31 PM ---------- Previous post was at 06:50 PM ----------
s4zw said:
I installed it and it boot to black screen, how to uninstall it please
Click to expand...
Click to collapse
Edit: I installed ROM again and it's booting up normally now, how can I use the driver . I really need it
EyeBalos said:
I've installed BeingTejas drivers and Kernel V5 combined ZIP file before this thread was created. Can I dirty flash this video driver over my existing one?
Click to expand...
Click to collapse
No, you need to reinstall the rom.
s4zw said:
I installed it and it boot to black screen, how to uninstall it please
---------- Post added at 07:31 PM ---------- Previous post was at 06:50 PM ----------
Edit: I installed ROM again and it's booting up normally now, how can I use the driver . I really need it
Click to expand...
Click to collapse
Follow the instructions, otherwise it will give you a black screen.
Added lastest android Q drivers (v415). Tested on MiMax 2 running SuperiorOS.
Just a side note: give the credits when you copy other people work, don't just copy and call your own.
It's not nice to do so, you can even make harm to the community as the original creator can stop his work and in the end you will get caught.
Great Work sir thankyou for updating driver
it's great that i find someone who do the work for Mi Max 2.
and unfortunately i read some argument on the top replies too.
what i've done on the past was just finding the latest version blobs for related adreno gpu. extract it from a rom, check the version, flash-test it, run the benchmark and test the vulkan features.
after that i analyze the logcat to see if there's something related to the graphics problem causing by the new drivers.
other than that, it's require reverse-engineering the blobs to fix the error (like blackscreen) which until today i haven't been advanced it because i didn't really dive into it.
Every time i install thise drivers Google camera on.mi max 2, turns black.. and Gg