Related
I tried getting Viper audio working today and pretty much hosed my Google Music. I have been running ressurection ROM for a while now which uses AudioFX and I grew tired of the lack of audio options. Also every time I reboot or even just randomly during the day my network drops and I have to choose another APN (although it never actually changes it just prompts the LTE to reconnect) which is super annoying.
So I read up on it flashed some IPS changed some settings and now Google won't play music which is my primary music player.
Any chance you guys can tell me which lolli based ROMs (without the LG skin) either are cooked with or have worked with Viper & Google music?
I've used the lolliviper.zip file located below many many times on AOSP based ROM's (including CM12.1) and never had an issue with it, aside from sometimes needing to download the selinux mode app to change selinux to permissive (although the OP now says if superSU is used then you don't need a full permissive kernel). Either way, it should work on all LP based ROM's including RR.
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Thanks. I did try with superSU first, then Busybox/selinux method, guessing there's just a menagerie of issues. I'm going to try Orion (did see it when I was searching around specifically for Viper before). Ty for replying
I am currently on MIUI 7 global stable and want to flash CM13. Can you please guide me to which are the options I have currently for :
- Good calls and call volume (I use 3G only..no LTE)
- Bluetooth pairing and music through bluetooth headphones
- Working Camera
- Fingerprint (I have a FPC102..checked via AIDA64)
No offense but I saw most of the devs mentioning in the bugs section "You Tell" but there are some ifs and buts..
I already have TWRP flashed..
Most of you might have already tried all the ROMS..hence asking your opinion..thank you dear friends and the wonderful devs
Official CM13 has almost no problems for me (I say almost because I haven't encountered any that haven't been fixed in a day or two). Fingerprint is faster than MIUI tbh. Must be because fingerprint is baked-in in android marshmallow. Don't have to bother with MIUI force closing apps (torrent apps always closed after some time in MIUI) . Multitasking is great! With MIUI my phone felt like a 1.5 GB phone with its aggressive memory handling. Regarding camera the camera quality may have degraded slightly or it may just be placebo. But the MIUI camera app is definitely nicer and faster. That's the only thing I'm missing from MIUI. Some people have problems like fingerprint not working (even if Aida show FPC102), battery always stuck at 2% or 50%, led not working etc with official Cm13 but none of those problems for me . So stability would probably depend upon your luck.
I haven't tried Santosh's CM13 as it is said to lock bootloader again. I have tried resurrection remix but some bugs like recent apps showing even Android system (which has been present since resurrection lollipop in all devices. It doesnt hinder much but Android system is not supposed to show in recent apps. To understand what I'm talking about, when you open say a YouTube link it shows menu for which app you would like to open the link with and even that will be present in the recent apps.) and data not working ( data may be fixed by now though). I haven't tried other because Official one satisfied me very much.
Try the official one for once and see if you have any bugs. If not restore MIUI. MIUI 8 is coming and it seems it has some cool features but nothing to bring me back to MIUI.
Hello everyone, im here to ask the comunity about a little problem present on many aosp based roms and is the low volume on thirdparty apps (Whatsapp, Snapchat, others) and my question is, someone know the way to fix this? I try to google it and search for support but i didnt find anything. I hope you can help me.
Have a nice day to everyone.
jodytejada said:
Hello everyone, im here to ask the comunity about a little problem present on many aosp based roms and is the low volume on thirdparty apps (Whatsapp, Snapchat, others) and my question is, someone know the way to fix this? I try to google it and search for support but i didnt find anything. I hope you can help me.
Have a nice day to everyone.
Click to expand...
Click to collapse
You can try Audio Compatibility Patch. It has worked for me on other devices, and the Dev just updated Samsung support two days ago. I'm about to give it a try myself. I have the same problem. Viper doesn't process audio from my browser. I believe it's a deep buffer issue. Only my system apps get processed. It should work without magisk too. Definitely read the post before flashing it. I've honestly never had an issue using it in the past though.
Correction, will not work without magisk! I can't get it flash using SuperSU for root. If you have magisk, I would definitely give it shot. I'm going to look into swapping my superuser so I can test it.
And there is a another mic problem in whats app only on AOSP based roms
Spaceminer said:
You can try Audio Compatibility Patch. It has worked for me on other devices, and the Dev just updated Samsung support two days ago. I'm about to give it a try myself. I have the same problem. Viper doesn't process audio from my browser. I believe it's a deep buffer issue. Only my system apps get processed. It should work without magisk too. Definitely read the post before flashing it. I've honestly never had an issue using it in the past though.
Correction, will not work without magisk! I can't get it flash using SuperSU for root. If you have magisk, I would definitely give it shot. I'm going to look into swapping my superuser so I can test it.
Click to expand...
Click to collapse
Let me be more speciffic on this problem, the problem is the mic on thirdapps using voip service like whatsapp, line, and others. (The robotic voice) i try to find the fix of this for any 3rdparty app.
Thak you for your response.
Lrdkenway said:
And there is a another mic problem in whats app only on AOSP based roms
Click to expand...
Click to collapse
This is not another mic problem, is the same present on all the aosp based roms for our devide, im testing the AOSP Extended 4.6 and AICP 7.1.2 and i fix every bug (low volume speaker, incall problems like low volume incall, low volume in record voice fixed too, but the unique bug i cant fix is the 3rdpartyapp robotic voice bug.
I hope to clear everything here and thakyou for your response.
jodytejada said:
This is not another mic problem, is the same present on all the aosp based roms for our devide, im testing the AOSP Extended 4.6 and AICP 7.1.2 and i fix every bug (low volume speaker, incall problems like low volume incall, low volume in record voice fixed too, but the unique bug i cant fix is the 3rdpartyapp robotic voice bug.
I hope to clear everything here and thank you for your response.
Click to expand...
Click to collapse
My mistake. I read AOSP, and for some reason thought stock touchwiz. I did some searching around, and it might be related to Ok Google. I found many reports saying that turning it off fixes the robotic voice. This might be a good place to start looking.
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
I know our device supports Treble but I didn' t see any successful installation with 9.0 GSI roms, always bootlooping..
phone bootloops so do not try it
TurkO546 said:
phone bootloops so do not try it
Click to expand...
Click to collapse
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Click to expand...
Click to collapse
Do you contacted @phhusson ?
SGH-i200 said:
Do you contacted @phhusson ?
Click to expand...
Click to collapse
I reached out for him in his thread so he should be aware, but I got no answer back probably because I couldn't provide logs of the bootloop (my device isn't unlocked yet). If you got any logs that you could provide him, please do so either in his thread in the treble forums or his github issues page.
https://github.com/phhusson/treble_experimentations/issues
Redcalibur said:
I reached out for him in his thread
Click to expand...
Click to collapse
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
SGH-i200 said:
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
It isn't anything special really. I just asked him if he might know any reason why it doesn't boot for our devices.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device?
Click to expand...
Click to collapse
Redcalibur said:
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
Click to expand...
Click to collapse
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
SGH-i200 said:
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
Click to expand...
Click to collapse
I think nearly every Pie Treble rom is based on this rom, so you got to wait for this one to get updated before the other ones also get updated. Most people are pretty happy with how they perform. We also need to get it to run first before he fixes device specific bugs, so if anyone can get him the logs of the bootloop, please do so.
Pontential solution
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Generic123. said:
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Click to expand...
Click to collapse
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
lilbrat said:
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
Click to expand...
Click to collapse
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Generic123. said:
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Click to expand...
Click to collapse
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Riskypedia said:
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Click to expand...
Click to collapse
You should first flash a stock firmware using newflasher or flashtool, then flash TWRP. Then factory reset or format using TWRP, and flash the GSI(AOSP ROM) and Magisk right after.
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
manxp85 said:
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
Click to expand...
Click to collapse
Are you still using one? Which one do you prefer? Resurrection Remix seems to do it for me.
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
manxp85 said:
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
Click to expand...
Click to collapse
Thanks for the info! Scrollable widgets seem to work for me(using calendar right now). The battery light does not work, like you mentioned. Auto update is also broken. Can't really test Bluetooth car audio right now. I'm bummed out by the lack of auto brightness.
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
manxp85 said:
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
Click to expand...
Click to collapse
Yeah, I'm using this month's build. I'll check car Bluetooth later when I get home.
PSA for @Wizballs and any other miPad 4 owners of the WiFI-only model...
Most of us have probably been looking for a ROM that is actively and officially developed that doesn't have the bug where it looks for the non-existing SIM card and drains the battery during standby. I'm happy to report that MoKee appears to use a different base than most ROMS for clover that are based on LineageOS, and MoKee 10 for clover seems to work really well. I left my device in Airplane mode for 7 hours, and the battery percentage was exactly the same as I left it. Finally!
删库跑路 - 马丁龙猪的博客
刷机的时代其实早已落幕，迟迟下不定决心只是希望能让魔趣多存续一些时间，但该来的终究会来。 马丁龙猪今天决定删库
download.mokeedev.com
A few other observations and first impressions:
I hate the tacky cartoonish boot animation, but the com.jrummy.apps.boot.animations app works fine to change it after rooting with Magisk.
For the initial setup screen the default option is Chinese, but just scroll down until you see your language, it appears to support all the usual ones.
I didn't install GApps, but somehow it still has the official Gboard keyboard with swipe enabled out of the box.
For some reason on my first install it didn't have a camera app. Then I wiped it and reflashed it and now it has a camera (org.mokee.snap). I honestly don't understand how it could be different from one flash to another, but at any rate it appears to be quite a nice camera with lots of configurable options and a working panoramic mode, which is rare in AOSP based ROMs.
The default gallery app is also good, SimpleMobileTools Simple Gallery Pro, which is my preferred open source gallery app. Some ROMs preinstall Simple Gallery, but it's not the pro version and it's much more limited, and it conflicts with the Pro version when you try to install it over top of it. MoKee does it right from the start.
Lots of configurability in the settings, including an option to control the cursor with the volume keys and on the bottom bar, which I find extremely useful. Only missing option is putting the date on the status bar next to the clock.
Working notification LED, unlike ArrowOS.
So this has been a great find. I'll report back if I find anything else. Thanks a lot to the devs if any see this thread.
Nice find and PSA
I just had a quick read about Mokee, and it appears to be a legit rom.
- From what I've read, playstore is installable
- States open source, get a tick for that
- Any chance you've run a quick virus/malware scan?
- I can see a few 'experimental' builds for 11.0, I'll keep an eye on that progress..
Cheers
Wizballs said:
Nice find and PSA
I just had a quick read about Mokee, and it appears to be a legit rom.
- From what I've read, playstore is installable
- States open source, get a tick for that
- Any chance you've run a quick virus/malware scan?
- I can see a few 'experimental' builds for 11.0, I'll keep an eye on that progress..
Cheers
Click to expand...
Click to collapse
Hi there, no I haven't run any malware scans, I don't have much faith in the antivirus/anti-malware sort of programs due to the false positives and FUD that they seem to depend on. I can give it a shot though if you know of any trustworthy ones.
Yes, the Play Store should be installable, they have normal Gapps packages that they recommend at the downloads page. I prefer to run with MicroG instead and I use the Aurora store. A small disadvantage is that MoKee doesn't support signature spoofing out of the box (needed for MicroG), but with Magisk and NanoDroid I got it working.
I also saw the 11.0 builds, maybe we should try to post over on their forum to let them know that there are some very interested and determined clover owners still out there.
sb56637 said:
Hi there, no I haven't run any malware scans, I don't have much faith in the antivirus/anti-malware sort of programs due to the false positives and FUD that they seem to depend on. I can give it a shot though if you know of any trustworthy ones.
Yes, the Play Store should be installable, they have normal Gapps packages that they recommend at the downloads page. I prefer to run with MicroG instead and I use the Aurora store. A small disadvantage is that MoKee doesn't support signature spoofing out of the box (needed for MicroG), but with Magisk and NanoDroid I got it working.
I also saw the 11.0 builds, maybe we should try to post over on their forum to let them know that there are some very interested and determined clover owners still out there.
Click to expand...
Click to collapse
The only scanner I really use is ESET for windows, and new android roms and then uninstall after scanning. I've never got a false positive from it.
But I'm downloading Mokee now to give it a try...
So far so good. I'll leave it sit now for 24 hours and report back on standby battery use. And yes I think posting a thanks in their forums is a good idea. And will just be a thanks as there are no real issues to report! Actually is a very well finished and working ROM.
Couple or more points:
- Mokee recommended gapps (opengapps) just wouldn't install - error code 64
- Nikgapps installed and ran perfectly fine however. lol.
- USB debugging turned on by default, some users like me will want to turn this off
- Does appear to be a lineageos base, but only a guess
- Can actually turn off double tap to wake. Arrow stayed on regardless of setting. Wonder if this will help standby battery marginally? I have flip case that turns screen on, works with this rom
- ESET scan 100% clean
- Disabled a few of useless apps (like I do with every ROM, without root) using:
adb shell
pm uninstall -k --user 0 package.name
- Nutflix not available directly from Playstore. Not a problem, install using SAI
- Encryption turned on by default (great!)
- Lately I'm finding that built in launchers are giving me the best stability / performance in any ROMS . Always used nova in the past.
- Turned off that status bar upload/download speed doobie. Personal preference.
- Appears to have OTA updater, will give a spin next update
Overall, awesome so far
Good find @sb56637
@Wizballs Great, and I'm glad it scanned clean too.
Appears to have OTA updater, will give a spin next update
Click to expand...
Click to collapse
Yep, although there are a few quirks here. First is that they limit the download speed to about 250 KB/s for non-donators, fair enough. But the bigger issue is that it downloads it to the internal storage (obviously), which MoKee automatically encrypts, so normal TWRP can't see it and it can't be installed. They supposedly have a MoKee flavor of TWRP that works with the encryption. I briefly tried to download it, but it was a Baidu site in Chinese that offered me Linux packages (DEB or RPM), which didn't make sense, so I stopped there. But I'll look into it more again and report back.
Fair enough, will stick to manual updates then. Would prefer to keep stock twrp.
Approx 2.5% battery over 24 hours standby. Very good.
I decided to switch to the MoKee flavor of TWRP, linked here in a more accessible location:
Android10.New Mokee MK100
Download: https://download.mokeedev.com/clover/file/MK100.0-clover-201912021712-EXPERIMENTAL.zip/download -First boot in cn language only. setting----System----Add Eng language to Gboard---deselect from CN to Eng in first order option you...
forum.xda-developers.com
With that flashed, OTA updates work well. (Plus it allows for manipulating /system and /data from the TWRP file manager, which is very useful sometimes. Plus, it allows for flashing other scripts like Magisk from TWRP, which adds an addon.d hook to allow it to survive upgrades.)
Wizballs said:
- Lately I'm finding that built in launchers are giving me the best stability / performance in any ROMS . Always used nova in the past.
Click to expand...
Click to collapse
Quick post to note that in later Android versions (from A10+?) the default launcher is always in charge of displaying recents, so it can't/shouldn't be uninstalled -- this may explain stability issues...
pnin said:
Quick post to note that in later Android versions (from A10+?) the default launcher is always in charge of displaying recents, so it can't/shouldn't be uninstalled -- this may explain stability issues...
Click to expand...
Click to collapse
I never uninstalled the default browser, just left it there while using nova...
Look at that battery saving. Worldwide could account to millions dollars saved each year
sb56637 said:
I decided to switch to the MoKee flavor of TWRP, linked here in a more accessible location:
Android10.New Mokee MK100
Download: https://download.mokeedev.com/clover/file/MK100.0-clover-201912021712-EXPERIMENTAL.zip/download -First boot in cn language only. setting----System----Add Eng language to Gboard---deselect from CN to Eng in first order option you...
forum.xda-developers.com
With that flashed, OTA updates work well. (Plus it allows for manipulating /system and /data from the TWRP file manager, which is very useful sometimes. Plus, it allows for flashing other scripts like Magisk from TWRP, which adds an addon.d hook to allow it to survive upgrades.)
Click to expand...
Click to collapse
Can you share the Mokee recovery via a different link? That link doesn't work and the one on Mokee's website points to Baidu, which seems to require a Baidu account to download. I can't create a Baidu account though, since it requires you to use a China mobile number to register.
UPDATE:
NVM, found the link via another XDA thread. Here it is:
TWRP-20200628-3.3.1.0-clover.img
drive.google.com
This ROM is missing face unlock, which isn't a big deal considering that the battery life is a big improvement over the last ROM I was using, but still would be nice to have...