Database Develop

[MOD] Drivelink (Mirrorlink) Full Mirroring

j0ep0 and I are currently working to get the mirroring that we were promised working with Drivelink and the Galaxy S III. Currently we have mirroring working successfully but there are a few bugs with the Drivelink app getting wiped and restarted. Here is a list of everything so far:
Full Mirroring without the drive link app resurfacing - Working (random restarts due to memory cleanup in android)
Work with Any Launcher - Currently Nova and Apex work
Reassigning the Home button -
Bypassing the two warning Messages -
Compatibility with Non-touchwiz Roms-
Compatibility with Other Devices -
Dim or turn off Phone screen when mirroring-
Automatically go into launcher (minimizing drivelink) -
Currently the setup we have is working for the following devices:
GSM Galaxy S III
CDMA Galaxy S III (No Data)
If it is working on your device please post, or PM me with the Following:
Carrier
Phone Model
Any Bugs
Rom/Kernel (If custom)
Installation Instructions:
Code:
Non-root:
Go into Settings and Enable "Install from Unknown sources"
Install the APK and run it.
Plug into your head unit and pray.
This method has worked for some (including myself) and not for others.
It will give you the standard Drivelink app and
no custom code by us, you need root for that.
Rooted users:
Download the TMServer zip to your Phone
Reboot into recovery and install (Like a ROM)
No need to wipe anything, you're just replacing
a system APK which is why you need root.
Install the Drivelink APK after enabling Unknown sources.
Run the Drivelink app and plug your phone into the head unit,
After accepting prompts you should see the drive link app.
There are several ways to get to your stock home screen but the easiest for me is to hold your home button down the bring up task manager, Click on another open app, when it opens hit the home button and viola, you're at your home screen. We are trying to find a way to bypass this but drivelink puts the phone into car mode and that disables the home button. Car mode is required to get the audio to route correctly to the head unit.
Here are the Links:
TM Server- Must be flashed in a custom recovery:
TMServer
Drivelink- Remove all versions, allow unknown sources and install this apk:
DriveLink
Both j0ep0 and myself have full time jobs and families so we are working very hard to get this working on our own time. So please be patient. We will get this working fully!
Nice description write up by Olywa123, Thanks
What is it
Drivelink is Samsung's application used to facilitate ‘Mirrorlink’ connectivity with supported car headunits. Currently their are several aftermarket car stereos by Sony, Alpine, and JVC that support this technology. The majority of users here have the Sony XAV-601BT headunit but it is believed the protocol for connection is the same for each. This standard is known as Mirrorlink (formerly Terminal Mode) and uses the VNC RFB3.8 protocol allowing for two-way communication between the smartphone and headunit over a usb connection for both display duplication and key-inputs and uses Bluetooth A2DP for Audio.
Videos
The following videos best provide a summary of this technology
Mirrorlink Overview: http://www.youtube.com/watch?v=sWNpK...eature=related
Example of MirrorLink on XAV-601BT: http://www.youtube.com/watch?v=BsT1l8bLOfU (shows Nokia and Samsung phone support)
Example of Drivelink App: http://www.youtube.com/watch?v=CHVmogapY9U
Why The Drive Link App needs Modification
Although Samsung have released the Drivelink application, this is not only very limited but also compatible only with the Galaxy SIII currently. It provides a ‘dashboard’ interface allowing for the use of only stock Music, Phone and Navigation (limited to Google maps) functionality. You cannot get back to your phones home screen or run any other apps while Drivelink is running/mirrored on the headunit and killing Drivelink kills the interface meaning the stereo no longer sees and mirrors the phones display. This appears to be a restriction coded into the Drivelink software as the video above shows that the Nokia interface allows for full phone control in addition to just the Nokia released Mirrorlink app on Symbian (Car Mode).

what is this actually
Sent from my GT-I9300 using xda premium

I haven't been following my other thread lately but you mention here you have CDMA version working without data. I'm in verizon gs3. How do I get this baby running even without data? I tried flashing that tmservice.zip abiut a week ago with no luck. Is this one a revised version ? I will try again anyways thanks
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
kp.nikhil said:
what is this actually
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Something like this. Except the goal here is to have full mirroring of the launcher and everything that's on the phone http://www.youtube.com/watch?v=CHVmogapY9U&feature=youtube_gdata_player
Sent from my SCH-I535 using xda app-developers app

Checking in for updates as the U.S. siii gets more progress (especially with cm10).

Verizon galaxy SIII with CM10 nightlies, and this is my result.

Updated OP with more information

Question... do you have to flash tmserver if you are using a rooted touchwiz rom?
Sent from my DROID3 using Tapatalk 2

If you use Touchwiz based Rom, first check in /system/tmserverapp.apk exists. If it is there, just install the DriveLink apk. If it's not, install this TMServer: http://www.mediafire.com/download.php?3926b2kuewyn84i.
(the one in OP is a test version).

So can I use Sony XAV601BT with a Verizon running CM10 nightly on 4.1.2
Sent from my SCH-I535 using xda app-developers app

Drive Link works on CM10, but the screen mirroring app doesn't.

3 weeks or so and I should have my Verizon Note 2 and will be back in this for some testing. assuming it doesnt just work right off.

it works! thanks!
but if I run Temple Run game, the USB link will fail.
I guess the memory killer may kill the tm server that cause USB link fail.
BTW,
I remember the USB link requires the CDC/NCM support in kernel or the mirrorlink cannot be activated, correct?

chinlin0924 said:
it works! thanks!
but if I run Temple Run game, the USB link will fail.
I guess the memory killer may kill the tm server that cause USB link fail.
BTW,
I remember the USB link requires the CDC/NCM support in kernel or the mirrorlink cannot be activated, correct?
Click to expand...
Click to collapse
What phone, carrier, rom are you using?
Sent from my SCH-I535 using xda app-developers app

Eureka!
Installed the DriveLink APK from the first post.
Carrier: Verizon
Phone Model: Samsung Galaxy SIII SCH-I535
Any Bugs: None that I could tell. I only played with it lightly for 15 minutes
Rom/Kernel: JellyWiz Stock [VZW LEAK] http://forum.xda-developers.com/showthread.php?t=1853337
Results:
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.

mrjoshzombie said:
Eureka!
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.
Click to expand...
Click to collapse
Nice to see that my mod is working for you
You're answering your own question, VZW is Samung based and has the Touchwiz framework. You can always switch launcher to Trebuchet or Nova to get a less "Touchwiz" sensation.

mrjoshzombie said:
Eureka!
Installed the DriveLink APK from the first post.
Carrier: Verizon
Phone Model: Samsung Galaxy SIII SCH-I535
Any Bugs: None that I could tell. I only played with it lightly for 15 minutes
Rom/Kernel: JellyWiz Stock [VZW LEAK] http://forum.xda-developers.com/showthread.php?t=1853337
Results:
So what does the leaked VZW have that CM10 doesn't? Because I can't stand TouchWiz anymore after months with CM10.
Click to expand...
Click to collapse
Strange... there must be something with that rom. I could never get my VZ S3 to work, but i never tried a jellybean rom.

read the sony thread. seems the device authentication is by key. i'm assuming the mysterious device identifier component is in that key. but i'm also assuming that the key code is closed on both the client and server. but just wondering if you've looked at that yet, j0e0p? if i recall you don't even have the deck?

shirazdindar said:
read the sony thread. seems the device authentication is by key. i'm assuming the mysterious device identifier component is in that key. but i'm also assuming that the key code is closed on both the client and server. but just wondering if you've looked at that yet, j0e0p? if i recall you don't even have the deck?
Click to expand...
Click to collapse
To do a little braindump, I've checked in /system/security/security/cacerts but can't find much differences between the several ROMs. In the code of the Drive Link app there are some checks in build.prop to identify the device but if that's really restricted the app shouldn't work on the Verizon as that device id isn't in the code. Finally I've found some references to the bootloader/kernel. That might be the cause.
I don't have the deck, the keying part isn't published in the source code from Sony and mirrorlink doesn't seem to be working on the latest XXDLJ4 (rooted) for i9300 which I'm running as my daily driver. Maybe someone could confirm that?

j0ep0 said:
To do a little braindump, I've checked in /system/security/security/cacerts but can't find much differences between the several ROMs. In the code of the Drive Link app there are some checks in build.prop to identify the device but if that's really restricted the app shouldn't work on the Verizon as that device id isn't in the code. Finally I've found some references to the bootloader/kernel. That might be the cause.
I don't have the deck, the keying part isn't published in the source code from Sony and mirrorlink doesn't seem to be working on the latest XXDLJ4 (rooted) for i9300 which I'm running as my daily driver. Maybe someone could confirm that?
Click to expand...
Click to collapse
I'm on xxdlj4 rooted as well and my works and connects perfectly.
Sent from my GT-I9300 using xda app-developers app

Is it possible to pull the framework from JellyWiz and insert it into CM10?

Launcher 8 problem (cannot add widgets)

I tried to add two widgets on the main screen on Launcher 8, but when i go to add->widgets, the screen flickers and returns back to main view. No option to select a widget. I was able before to add using Go Launcher, so the tablet lets me... problem must be within Launcher 8 app... any ideas?
Thanks.

Same problem here. Maybe it is a Nook specific problem :/

scio said:
Same problem here. Maybe it is a Nook specific problem :/
Click to expand...
Click to collapse
Doesn't seem logical ... the tablet is just a small computer, running some OS (android, in this case). Maybe is the android version (nook uses a pretty old android) ?

derei said:
Doesn't seem logical ... the tablet is just a small computer, running some OS (android, in this case). Maybe is the android version (nook uses a pretty old android) ?
Click to expand...
Click to collapse
Maybe it's magic?
Check the error message using logcat and then return after looking for that message in the search engine.

derei said:
Doesn't seem logical ... the tablet is just a small computer, running some OS (android, in this case). Maybe is the android version (nook uses a pretty old android) ?
Click to expand...
Click to collapse
Nook has Anroid 2.1 and a nook specific kernel - this will be the problem.

I am unable to edit the tiles, It takes me to the home screen whenever I try to edit it, I am using a Moto X Play with an updated android version and an updated WP Launcher application.

How do I enable tablet apps on my N6 from Google Play?

Scrolls just came out on Android tablets and Hearthstone is due out later this month but again only on tablets.
How do I spoof the play store into thinking I'm running a tablet? Is it as simple as editing the build.prop to be an HTC Nexus 9?
I used to be able to do this with xposed, but we all know that's not available on the Nexus 6 yet.
Thanks!

Yes. Just changed the build prop to mimmick the device you want. You might also need to change the DPI to get the app to play well on your phone..

About20ninj45 said:
Yes. Just changed the build prop to mimmick the device you want. You might also need to change the DPI to get the app to play well on your phone..
Click to expand...
Click to collapse
Thanks!
I adjusted the DPI from 580 to 480.
I changed the manufacturer from motorola to htc, and model from nexus 6 to nexus 9.
I cleared the play store data and rebooted.
It worked! Thanks again!

Well, it downloaded the app, but unfortunately it hangs on the initial logo display screen. Not sure if it's an android 5.0 issue or what. I adjusted the DPI all the way down to 260, no go.

Sirchuk said:
Well, it downloaded the app, but unfortunately it hangs on the initial logo display screen. Not sure if it's an android 5.0 issue or what. I adjusted the DPI all the way down to 260, no go.
Click to expand...
Click to collapse
I think since the nexus is the only android 5.0 phone out, aside from other nexus and international phones, you may have to wait for the developer to update the app to play friendly with 5.0. I would ask a htc nexus user or read reviews in the app store to see if anyone has it working correctly.

It actually works, it was my network at work blocking whatever the app was trying to use internet access for, so it hung instead of giving an error. Once I left work and was on cell phone or my home connection it loaded up just fine! Haven't had a chance to really play yet, but I can!

I am trying to do the same and followed your steps and didn't work. I am running CM 12 ROM however. Do you mind posting the changes you made to Build.prop so I can compare? I changed Manufacturer to HTC and Model to Nexus 9 and DPI to 480 and no-go. Play Store still sees it as not compatible.
Thanks

sabre31 said:
I am trying to do the same and followed your steps and didn't work. I am running CM 12 ROM however. Do you mind posting the changes you made to Build.prop so I can compare? I changed Manufacturer to HTC and Model to Nexus 9 and DPI to 480 and no-go. Play Store still sees it as not compatible.
Thanks
Click to expand...
Click to collapse
There is no need to do all of that, see http://forum.xda-developers.com/nexus-6/general/guide-link-how-to-play-hearthstone-t2975409

Cyanogen Mod and screen casting

This may be a known issue, but up until yesterday I thought it was only me.
Screen casting on any cyanogen ROM ends immediately after connection. Seems to happen regardless of cm ROM (cm12, cm11, resurrection, liquid) or device (moto x, bionic, kindle fire).
Is there a workaround?

metaljr81 said:
This may be a known issue, but up until yesterday I thought it was only me.
Screen casting on any cyanogen ROM ends immediately after connection. Seems to happen regardless of cm ROM (cm12, cm11, resurrection, liquid) or device (moto x, bionic, kindle fire).
Is there a workaround?
Click to expand...
Click to collapse
Might be your device? I'm running cm11 and broadcast to my chromecast just fine.

93Akkord said:
Might be your device? I'm running cm11 and broadcast to my chromecast just fine.
Click to expand...
Click to collapse
He is refering to the Cast Screen feature.
It is not working on any CM roms.

crashtheface,
Thank you! This has been driving me nuts the last few days.
I have a Sprint SGS3 (SPH-L710) running CM11 (cm-11-20141008-SNAPSHOT-M11-d2lte).
This one did not work for me:
http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
I just got this one to work, but it is very laggy. It take 6 to 7 seconds to refresh the screen each time I switch apps.
https://play.google.com/store/apps/details?id=com.mobzapp.screenstream
I am really surprised that CM11 does not have screen mirroring to ChromeCast already built in.
I suspect is may be hardware related.
Thx...

crashtheface said:
He is refering to the Cast Screen feature.
It is not working on any CM roms.
Click to expand...
Click to collapse
Yup, cast screen worked for me just fine as well. No issues. Guess I'm lucky then

JM-PDA said:
crashtheface,
Thank you! This has been driving me nuts the last few days.
I have a Sprint SGS3 (SPH-L710) running CM11 (cm-11-20141008-SNAPSHOT-M11-d2lte).
This one did not work for me:
http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
I just got this one to work, but it is very laggy. It take 6 to 7 seconds to refresh the screen each time I switch apps.
https://play.google.com/store/apps/details?id=com.mobzapp.screenstream
I am really surprised that CM11 does not have screen mirroring to ChromeCast already built in.
I suspect is may be hardware related.
Thx...
Click to expand...
Click to collapse
It doesn't seem to currently be hardware related.
All my devices run cast screen fine with AOSP stock 4.4.2 and 4.4.4 roms. However when going to say SlimKat, CM, or other 3rd party roms it fails.

#MirrorEnabler – CM11 KK 4.4 fix! (Well this worked for me)
On my nook HD plus running PacRom RC3 cm11 4.4.4
With root access (I used X-plorer)
Step 1:
Go to "/data/app-lib/com.r3pwn.mirrorenabler-1/"
Copy the 2 files
"libaudiopolicyconf.so" and "libhackyworkaround.so" to this directory "/data/data/com.r3.pwn.mirrorenabler/"
Step 2:
Go to "/data/app-lib/" and copy "com.google.android.apps.chromcast.app-1" into "/data/data/com.google.android.apps.chromecast.app/"
step 3: apply mirrorenabler settings and reboot....

krypticn said:
#MirrorEnabler – CM11 KK 4.4 fix! (Well this worked for me)
On my nook HD plus running PacRom RC3 cm11 4.4.4
With root access (I used X-plorer)
Step 1:
Go to "/data/app-lib/com.r3pwn.mirrorenabler-1/"
Copy the 2 files
"libaudiopolicyconf.so" and "libhackyworkaround.so" to this directory "/data/data/com.r3.pwn.mirrorenabler/"
Step 2:
Go to "/data/app-lib/" and copy "com.google.android.apps.chromcast.app-1" into "/data/data/com.google.android.apps.chromecast.app/"
step 3: apply mirrorenabler settings and reboot....
Click to expand...
Click to collapse
You don't need it anymore. Google updated chromecast app. Any devices running 4.4.2 should have mirroring enabled by default. I didn't try it on my nook yet, but I think it'll work without this app.

I could only cast for about half a sec. than it would immediately disconnect on both 4.3 and 4.4 PAC-Rom but by doing the above I was able get screen cast to work.
Sent from my BN NookHD+ using XDA Free mobile app

Based on my recent experience, it wasn't working for me on CloudyG3 1.2 (didn't try 2.0 yet - it was connecting and immediately disconnecting, with few tries results into dark screen on Chromecast), however on Darkobas PSD (ParanoidSabreDroid) Lollipop ROM (AOSPA rom) working without any issue and really very fast. (http://forum.xda-developers.com/lg-g3/development/rom-darkobass-psd-rom-dark-material-t2978382) (sorry, al LG G3 - D855 ROMs)

crashtheface said:
He is refering to the Cast Screen feature.
It is not working on any CM roms.
Click to expand...
Click to collapse
Works fine for me on CM12 !! Works flawlessly like a charm !!

tharmor said:
Works fine for me on CM12 !! Works flawlessly like a charm !!
Click to expand...
Click to collapse
hmm I'm wondering if the devs working on your motoG CM12 branch implemented it? I have yet to hear of any other CM builds where this has been successfully implemented.

crashtheface said:
hmm I'm wondering if the devs working on your motoG CM12 branch implemented it? I have yet to hear of any other CM builds where this has been successfully implemented.
Click to expand...
Click to collapse
It works on stock as well on Moto G !!! So should work on CM 12 !! Mine is galaxy grand duos and moto G and it works fine for me !!

tharmor said:
It works on stock as well on Moto G !!! So should work on CM 12 !! Mine is galaxy grand duos and moto G and it works fine for me !!
Click to expand...
Click to collapse
Are you sure you aren't refering to basic cast from App?
I'm talking about Cast Screen, the beta feature which DIRECTLY MIRRORS YOUR HANDSET SCREEN to your chromecast.
You may be confused as there are literally no reports or success stories of CAST SCREEN and not Google Cast.
They are two completely different things we are discussing screen mirroring in this thread.

crashtheface said:
Are you sure you aren't refering to basic cast from App?
I'm talking about Cast Screen, the beta feature which DIRECTLY MIRRORS YOUR HANDSET SCREEN to your chromecast.
You may be confused as there are literally no reports or success stories of CAST SCREEN and not Google Cast.
They are two completely different things we are discussing screen mirroring in this thread.
Click to expand...
Click to collapse
Watching your mobile screen on Chromecast !! Hope this is clear to you now !! Yes i am talking about screen mirroring dude !!
CM12 is on my Galaxy grand and not moto G yet !!

tharmor said:
Watching your mobile screen on Chromecast !! Hope this is clear to you now !! Yes i am talking about screen mirroring dude !!
Show some respect !!
Click to expand...
Click to collapse
just making sure friend. there has been confusing from time to time
what exactly was your method? I see two cast icons in your notifications area.
Also can you link me to your rom page on xda? I would like to contact the devs who did the build to see if they had manually changed anything to allow for cast screen.
I'm excited to go back to CM if I can get Cast screen working on my devices with Cyanogenmod.

crashtheface said:
just making sure friend. there has been confusing from time to time
what exactly was your method? I see two cast icons in your notifications area.
Also can you link me to your rom page on xda? I would like to contact the devs who did the build to see if they had manually changed anything to allow for cast screen.
I'm excited to go back to CM if I can get Cast screen working on my devices with Cyanogenmod.
Click to expand...
Click to collapse
Check with @pawitp here on xda .... He is a legend for our phone !!
Second notification was from dailymotion which I did not close when i started screen cast !!

tharmor said:
Check with @pawitp here on xda .... He is a legend for our phone !!
Second notification was from dailymotion which I did not close when i started screen cast !!
Click to expand...
Click to collapse
ah he does not accept private messages. can you link me to the thread pertaining to your rom?

crashtheface said:
ah he does not accept private messages. can you link me to the thread pertaining to your rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2942255

tharmor said:
http://forum.xda-developers.com/showthread.php?t=2942255
Click to expand...
Click to collapse
cheers!

Official Android M Discussion Thread

I've already seen that on the M Developer preview WiFi calling is working on the T-Mobile Nexus 6. Can anyone who has updated to the M preview on a Nexus 5 confirm if WiFi Calling is now baked into the OS like it is with iOS?

taino211 said:
I've already seen that on the M Developer preview WiFi calling is working on the T-Mobile Nexus 6. Can anyone who has updated to the M preview on a Nexus 5 confirm if WiFi Calling is now baked into the OS like it is with iOS?
Click to expand...
Click to collapse
it has been since 5.1 on the n6,the n5 will not get (afaik)

Lets discuss Android M Here. Lets talk about features/bugs, tips & tricks !
Official Download:
https://developer.android.com/preview/download.html#top

Google introduced that nifty tap Google now feature but for me it says it's not available. Anyone else experiencing this issue?

It's going to be available in the release version

Have any of you rooted the Android M?
After I flash the UPDATE-SuperSU-v2.46.zip into the device, it won't boot, just stuck at the booting animation.
Any ideas?

zhangcx93 said:
After I flash the UPDATE-SuperSU-v2.46.zip into the device, it won't boot, just stuck at the booting animation.
Any ideas?
Click to expand...
Click to collapse
Fastboot flash the system image and possibly boot to get this fixed or alternatively rum flash all again. SuperSU has not been updated yet for M.

defconoi said:
Fastboot flash the system image and possibly boot to get this fixed or alternatively rum flash all again. SuperSU has not been updated yet for M.
Click to expand...
Click to collapse
That helped. I did flash the system.img back to boot again, still without root.
Expecting the lastest supersu update!
Actually some news site says it works to root the android m, so i tried, and failed...
thxs

Anyone else have 100% wake issue. Phone doesn't seem to be sleeping

I don't like the new app tray

Native multiwindows support is available. You need to edit the build.prop and change ro.build.type to userdebug and it will show up in developer settings.

markdapimp said:
I don't like the new app tray
Click to expand...
Click to collapse
It will take some time to get used to it. I like it and the fact that the recent apps are shown above is great. Saves time.
Sent from my Nexus 5 using XDA Free mobile app

WiFi calling came to the Nexus 6 with LYZ28E, Android 5.1.1. I have yet to see WiFi calling working on Android M. Does anyone have a link to that? I would like to see someone port LYZ28E to the Nexus 5 though. Hopefully sooner than later as I can't think of any reason why it couldn't be ported by the right person.

Interesting tweaks to the lock screen: updated font weights and styles and also the dialer app shortcut is replaced with voice search. I like that you now have to swipe from the app shortcuts to launch them instead of just swiping to either side; I occasionally would launch the camera or phone app by accident when unlocking before.

Take this: SuperSU 2.49 Beta
Maybe it works, im downloading now.

jcsww said:
WiFi calling came to the Nexus 6 with LYZ28E, Android 5.1.1. I have yet to see WiFi calling working on Android M. Does anyone have a link to that? I would like to see someone port LYZ28E to the Nexus 5 though. Hopefully sooner than later as I can't think of any reason why it couldn't be ported by the right person.
Click to expand...
Click to collapse
A couple people on Reddit with Nexus 6 M preview installed said T-Mobile WiFi calling is working.
http://www.reddit.com/r/nexus6/comments/37mmth/android_m_developer_preview_images_up/crnzete

Apps I have that are not working:
Waze - Crashes on launch and causes background to turn and stay black until reboot
Uber - Crashes on launch
Evernote - Crashes on launch
Camera seems to crash randomly
Mostly app issues, but not sure when they'll get updated. I'd stay on M, but need Waze and Uber for some travel in upcoming days.

I love the new app tray, I once saw that in a custom rom on a device of a friend and I loved it.
If someone has errors while it should flash the system try to flash it by hand:
Code:
fastboot flash boot boot.img
then
Code:
fastboot flash cache cache.img
and continue with that system till the last .img.
Yes you always have to put the folder name in front of the .img (folder name = .img without .img)
after you manually installed those you have to execute "flash-base.sh" NOT FLASH-ALL.CMD OR YOU HAVE TO REDO FLASHING THE .IMG'S!!!
Oh and who wants to record 4k 30fps without flashing anything, THIS APP:
Snap Camera HDR: TRIAL // FULL (1.49€)
-> 4k Recording 30fps (Slightly scaled as the width is the same)
-> 3.4k Recording 30fps (Native Resolution)
-> 1440p Recording 60fps
-> 1080p Recording 120fps
(you can take the trial, just dont press the close button and wait the 10 seconds. I bought it my self cause its really worth it!)

xvanwilderx said:
Apps I have that are not working:
Waze - Crashes on launch and causes background to turn and stay black until reboot
Uber - Crashes on launch
Evernote - Crashes on launch
Camera seems to crash randomly
Mostly app issues, but not sure when they'll get updated. I'd stay on M, but need Waze and Uber for some travel in upcoming days.
Click to expand...
Click to collapse
PowerAMP is crashing too.Anybody can confirm please?

No issues here..... yet. I do like what they are doing with the battery saving. Can't wait to see what else happens!