Search results

Then you have perhaps bought the Pro version of Flashfire? The standard free Playstore version has a built in time bomb that cause it to abort if the date is too recent. And since chainfire has stopped development, updated version with extended time limits will not be built. Thanks for the...

If I understand you correctly you have access to fastboot. Then why not just register with the Nvidia developer program and download from there: https://developer.nvidia.com/gameworksdownload There you can pick any version you'd like to install, they've even got the new 7.0.1 developer images...

Does the official TWRP recovery work on 7.0.1 (Oreo)? If so does rooting with Magisk / SuperSU also work?

Do you have an official statement from Huawei on this? I've been in contact with Huawei and the response I've got is that the unlock site is temporarily down for maintencance. If it's permanently down I'd be seriously disappointed since I just received a P20 Pro today, and that would render it...

That seemed to solve the problem. Thanks!

Sorry, I did not specify. This is on KingRom, so regular kernel, not N7. I've tested with Kernel versions 1.5.2, 1.5.3 and 1.6.0. Same problem on all of them, traffic does not get routed through VPN connection.

I'm experiencing problems with VPN connections using this Kernel. The VPN connects fine, but traffic is not routed correctly through the VPN connection. I've tried both OpenVPN and PPTP (built in) and the behaviour is the same. If I flash a stock kernel things are working fine. Anyone else...

Did some more testing and this is kernel related. Flashed KingRom with stock kernel and VPN is working fine. Reflashed Prometheus and it stopped working again.

Anyone else have problems with VPN connections? I come from stock ROM where I had functional OpenVPN and PPTP (built in VPN). When I set up the VPN in this rom it connects fine, but the vpn interface address and routing tables does not get set up correctly.

I got my phone almost a week ago. It's been running APD1 all the time and I've been reasonably happy with battery life. Yesterday afternoon I turned on bluetooth and paired a couple of devices. Then I left it idle over night (still with bluetooth on, but not with any connected devices) and...

There's no option to download the log files as far as I can see. Can they give a specific location for the file they want?

Great work! I tried to follow the link to the wiki on your bitbucket, but only get a message that I don't have access to it. Maybe some permissions that should be changed?

The response from Teamviewer is that the SATV is not currently supported, and that device support is added by popular demand. So the more people who contact them, the better.

On my Shield I can connect to Teamviewer Host, and I can bring up the desktop. When I try to mouse click on the desktop, the whole machine reboots (this is with root access). I've got a dialog with Teamviewer support about this issue.

Reflashed the recovery once more and booted the recovery kernel. Suddenly TWRP was working and I could flash SuperSU.

I received a new Shield Android TV Pro yesterday and tried this procedure to root it. The 'fastboot oem unlock' took about 90 minutes and seemed to work ok. Then I pushed the recovery with This also seemed to work ok. Then I rebooted and tried to enter recovery with Unfortunately this only...

I can confirm this problem, see attached logcat. The problem seems to be this: E/installd( 314): Couldn't opendir /data/data/com.teamviewer.quicksupport.addon.aosp: No such file or directory W/PackageManager( 2078): Package couldn't be installed in...

I've been trying to install Render kernel on RR 5.5.3 for some time now, and no matter what I try I end up with a bootloop. So I hooked it up to a my PC and did an 'adb logcat' during the bootloop - see attached file. What I found is that the bootloop is caused by the ThermalEngine...

Using RR 5.5.3 this solution worked the first time around and everything seemed fine. After a reboot I ended up with a bootloop, and I'm unable to get Render Kernel to boot redoing the steps described. I've even tried a full wipe and reinstall. Now there is no way to boot with Render kernel and...

I can confirm this problem. It started with the 0702 build (which I clean flashed), and it's still there on the latest 0706 build. Previous builds worked fine. My provider does not have full national coverage so I am for the most part roaming. I can not get data roaming to work, and the...

I was too quick. After a while I'm now seeing 27Mhz as well. I'm on the version from the 16th.

That worked, thanks. But looking in Aduitor I still don't see the GPU drop below 200MHz.

Tried this on my d802 with latest Bliss nightly, did not manage to get it booting. I get a short message about "Secure booting error". Which bootstack are you on? And did you just replace the boot.img, what about the kernel modules in /system/lib?

Did you try the new LP bootloader button combination? It is VolDown+Power, release, then VolDown+VolUp.

I decided to try this ROM and thought sticking with the "official" release would be a good idea. So I followed the instructions in the OP and flashed the LP bootloader/modem combo linked to from post #2, and then flashed 3.2 official. Initially I had all kinds of problems with modem dropping...

No immersive mode or ability to hide navbar in L5 currently?

Latest release is 8.0.1, so that would probably be the best starting point: http://forum.xda-developers.com/showthread.php?p=55850278&highlight=8+0+1#post55850278

Pedometer/step counter broken The hardware step counter does not work, so the statement that "All accelometers/sensors" is working is a slight exaggeration. I'm using this app, and it does not count anything: https://play.google.com/store/apps/details?id=de.j4velin.pedometer&hl=en

How about searching the thread for "8.0.1" instead of cluttering the thread with inane questions: http://forum.xda-developers.com/showthread.php?p=55850278&highlight=8+0+1#post55850278

Then it's not interesting. I'm talking about the built in step sensor, which is very accurate and uses (almost) zero battery.

But is that using the hardware sensor?

Pedometer/step counter broken I just updated from Vanir 10/23 to 10/27, and found that the pedometer sensor does not work anymore. It has been working in all previous releases. Anyone who is savvy enough to go through the changelog and point at the likely culprit? This is using dorimanx 8.0.1...

Thanks for the confirmation. I just updated to the latest Vanir (10/27) just to find the pedometer broken there as well. It is working in the previous Vanir release (10/23). Will post in the Vanir thread as well.

Pedometer/step counter is broken There is something in the Mahdi Rom that breaks the Pedometer/StepCounter sensor. I'm using this pedometer app: https://play.google.com/store/apps/details?id=de.j4velin.pedometer&hl=en It uses the hardware sensor and has been working great on latest...

bart452 Seems like I spoke too soon. I see several problems, but the biggest one is that the device never wakes from sleep when it is disconnected from external power. Apart from that there are a few other issues, like this message in the log files: msm_ipc_router_send_to: permission failure...

blastagator Great work, thanks for posting this. Using your recovery and following the instructions in post #2, I now have F2FS working on /cache and /data with latest Vanir and Dorimanx 8.0.1 on my d802. I did manage to keep most of my old apps and settings. Just made a full Nandroid backup...

The instructions specifically states that you should back up your SD card. If you install experimental software and don't follow the instructions, you will lose data. In fact if you install anything and ignore the instructions, you will likely end up losing data. F2FS is a new filesystem. In...

My TWRP 7.8.0.1 has MTP enabled by default, I assume this is true for the F2FS enabled recovery from bart452 also. Unfortunately the d802 version does not work for me, so I cannot verify that.. If not MTP is working you can always sideload it, or copy it manually using adb push.

Got it to boot up by running loki_patch on it. But I'm not able to convert file systems to F2FS, I only get the error "vfork failed" when I try to convert /data.

Can't get the D802 recovery.img to work, it seems to be corrupt. Tried to flash with loki_tool and only get "Input file is not a Loki image". Also tried to flash manually with "dd", and it resulted in a corrupt recovery. I've tried to re-download, but just can't get it to work.

Found the problem. Had not reflashed kernel. Flashed 7.8, but it still did not work. Flashed the 7.9 test version for d802 and, voila, floating windows is working fine again.

I enabled Hover a couple of versions ago, and it was working as expected. On the latest version I can't get floating window to work, all apps start up normally filling the whole screen. Is this just on my device? On a D802.

I clean flashed latest (Vanir) ROM and kernel yesterday. No problems with sensors. Also on a D802.

SIM Toolkit is missing (at least in the 0809 release). Restoring the one from 0629 worked fine.

Reflashed baseband and redownloaded 0810 just to make sure, wiped and installed. I still get a boot loop. 0809 version works just fine. d802 and TWRP 2.7.1.0

I did some more tests, and on my device (d802) the 0810 version will bootloop even on a clean install. 0809 version works just fine.

Confirmed. I can dirty flash from 0629 to 0808 (CM kernel) or 0809 (AOSPA kernel), and everything works fine. When I dirty flash 0810 on top of either 0809 or 0629 the device keeps rebooting. This is on a D802.

houstonn Any chance of implementing support for the USB Keyboard app? As far as I can see it only involves adding the kernel-3.4.patch from this github repository: https://github.com/pelya/android-keyboard-gadget

houstonn National Data Roaming is still not working. I realize this might not be a specific problem to G2 version of PA. If so could you point me the right place to report this? My provider use MCC+MNC 24205 (Network Norway) , but I also roam on MCC+MNC 24201 (Telenor). The details I get from a...

I'm in a similar situation. My provider is Network Norway (MCC 242 MNC 05), but also roam for free on Telenor (MCC 242 MNC 01). I used to fix this with the National Data Roaming option, but it is no longer present. dr87 any hope of getting this into a future release?