Hi All,
I have rooted, installed safestrap, and flashed a rom slot with the google edition that was reported to work here. I flashed the MF3 master patch and also the active call recording patch to resolve a speakerphone issue (here).
Almost everything seems to be working fine but for 2 issues:
1. my camera's viewfinder is very grainy/pixelated when in video mode (this apparently isn't an issue on some other ROMs, more research on my part needed here)
2. when booted in the Google edition ROM, I can't get my computer to mount the file system via USB. Windows device manager indicates the device cannot start When I boot back into stock, it connects to my computer just fine.
I'm going to try to reflash this because when I originally installed this, I jumped the gun and rebooted before wiping dalvik, etc.
I'm also going to try reinstalling the drivers, but it works when I use the stock ROM, so I think drivers are fine.
Any other thoughts on this?
hrtendrup said:
Hi All,
I have rooted, installed safestrap, and flashed a rom slot with the google edition that was reported to work here. I flashed the MF3 master patch and also the active call recording patch to resolve a speakerphone issue (here).
Almost everything seems to be working fine but for 2 issues:
1. my camera's viewfinder is very grainy/pixelated when in video mode (this apparently isn't an issue on some other ROMs, more research on my part needed here)
2. when booted in the Google edition ROM, I can't get my computer to mount the file system via USB. Windows device manager indicates the device cannot start When I boot back into stock, it connects to my computer just fine.
I'm going to try to reflash this because when I originally installed this, I jumped the gun and rebooted before wiping dalvik, etc.
I'm also going to try reinstalling the drivers, but it works when I use the stock ROM, so I think drivers are fine.
Any other thoughts on this?
Click to expand...
Click to collapse
Both are well documented bugs. The video thing doesn't affect the actual recording. Playback looks normal. The USB thing: I think that's the case with all GPE ROMs.
Sent from my Nexus 7 using Tapatalk 4
Related
Soooo I've been using cm7 since it was still nightly 1 but I havent really had any wonk issues. However recently my camera, no longer works, the app loads fine but when you attempt to take a pic it force closes.... Heres where it gets strange apps that use the camera like google docs the camera works fine.... The other camera apps in the market work fine just not the stock camera app..
Has any one else had these issues?
Sent from my Nexus One
Has this occurring since you flashed it, or did it develop afterward? I would try clearing camera data see what happens.
it was random and I tried wiping camera data but I also tried reloading from titanium still no fix
Then maybe you will need to either factory reset or do a clean install.
Similar story
My camera app randomly stopped working recently. Not upon an update, but randomly. (CM7 stable) I wiped the device, reflashed the ROM/Gapps, and it still is broken. When you tap to launch it, it just restarts the device (same if launched from another app, such as barcode scanner, etc.). I also tried deleting its data, to no avail.
Anybody figure this out?
What version is your radio/baseband (Settings -> About Phone -> Baseband)? We go off the two sets of numbers after the underscore "_". Something like 4.06 or 5.08...
Mine's 5.08.00.04
Try a more recent version of CM7. Much have been updated since RC1.
If still having problems a clean wipe usually does the trick.
Sorry, my bad. This problem started with CM7. I then clean wiped and tried CM7.1.0 RC1, and that's what's running right now (with no difference on the camera).
When you wiped the device, was this through ROM Manager? If so, you may want to try a system-only wipe. Under clockworkmod you can do it in the mounts and storage menu. If you are running amon_ra, you will need to use a flashable zip that will wipe it for you. Temasek has one somewhere in here http://mediafire.com/temasek
Then reinstall CM and gapps. This won't cause any data loss.
I had wiped it from ROM Manager, so I followed your instructions (I am running clockworkmod). Unfortunately, that didn't change anything.
I been running CM7 stable for two weeks and that is one complain I have the picture quality sucks compare to stock android, I have to play with the contrast,saturation and sharpness every time to take a decent picture. As Far as the Camera bugging out on me I don't have any issues.
Did anyone manage to fix this problem WITHOUT taking it to the service centre?
For some reason, I still believe this is a software issue and not a hardware one.
Anybody?
Yeah, my feeling is it has to be software too, but I can't for the life of me seem to solve it. Anybody else have this issue??
Sent from my SAMSUNG-SGH-I727 using XDA
this solved my camera FC problem
http://www.ebay.com/itm/31037916447...X:IT&_trksid=p3984.m1497.l2649#ht_1535wt_1185
Two days ago i rooted my phone with VRoot, but now after i tried to install a new app i found, it said i couldn't and then i went to settings, checked Unknown sources, but after i back it is no longer checked, also some apps are crashing randomly.
One thing i did was using the Market enabler/DroidVPN method to unlock the us play store only to find out it does not work, i would say after i did this my phone started acting all weird
edit: phone is also randomly freezing
ppgab said:
Two days ago i rooted my phone with VRoot, but now after i tried to install a new app i found, it said i couldn't and then i went to settings, checked Unknown sources, but after i back it is no longer checked, also some apps are crashing randomly.
One thing i did was using the Market enabler/DroidVPN method to unlock the us play store only to find out it does not work, i would say after i did this my phone started acting all weird
edit: phone is also randomly freezing
Click to expand...
Click to collapse
My best advice to you is backup your personal data, and reflash with odin, you can also flash custom rom, recovery + kernel with the odin packages supplied by the maclaw team or flash stock .
sheephog said:
My best advice to you is backup your personal data, and reflash with odin, you can also flash custom rom, recovery + kernel with the odin packages supplied by the maclaw team or flash stock .
Click to expand...
Click to collapse
thanks for the reply, what i did was install cyanogenmod 4.4.2, everything is fine so far, i don't understand much about flashing and roms and stuff.
Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks
I have the Same Problem
I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?
Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?
So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.
There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.
I have a Verizon HTC One M8 (rooted, S-Off, TWRP, unlocked bootloader) that I have finally upgraded from 4.4.4 to 6.0. To prevent any possible radio problems I read about I did a factory reset from the bootloader screen to ensure a fresh install. After making sure that the Marshmallow worked fine I flashed the ARM framework 85 through TWRP and then installed the Xposed app. Now I am stuck where it is not working and I have searched but could not find anyone with the same problem here. I'll include a screenshot so that you know what I mean.
Tonysil said:
I have a Verizon HTC One M8 (rooted, S-Off, TWRP, unlocked bootloader) that I have finally upgraded from 4.4.4 to 6.0. To prevent any possible radio problems I read about I did a factory reset from the bootloader screen to ensure a fresh install. After making sure that the Marshmallow worked fine I flashed the ARM framework 85 through TWRP and then installed the Xposed app. Now I am stuck where it is not working and I have searched but could not find anyone with the same problem here. I'll include a screenshot so that you know what I mean.
Click to expand...
Click to collapse
Have you installed your modules, enabled them, and rebooted?
cali4niasunshine said:
Have you installed your modules, enabled them, and rebooted?
Click to expand...
Click to collapse
They were check and I had. Just to see I unchecked them all, rebooted, and then tried again and it looks like some but not most are working. Thank you, at least it's a start.
Tonysil said:
They were check and I had. Just to see I unchecked them all, rebooted, and then tried again and it looks like some but not most are working. Thank you, at least it's a start.
Click to expand...
Click to collapse
I had the same problem the first time I upgraded from Kit Kat to Marshmallow. My problem was that when I upgraded I reflashed the same modules that I had been using on Kit Kat..I found the modules that weren't working, uninstalled them, then re-installed the appropriate versions for Marshmallow (enabled the modules and rebooted) and everything worked great.. if this applies to you then give it a shot.
As far as your screenshot everything is working perfectly
I'm assuming that perhaps the unusable install/update and uninstall buttons maybe confusing you. That's normal those buttons no longer do anything they are only eyecandy at this juncture.
All versions must (at this time) be installed in Custom Recovery for those three functions. I hope I'm understanding your issue