Related
I try ROMs and ROMs and ROMs and all are unusable, because the
phone freezes with nameless-5.1.1-20151107-p880-nightly or
reboots when starting apps with euphoria-os-1.1-p880-unofficial-20160208-user or
is extremely slow and is stottering with aosplp-20151122-p880
a..s.o
The apps which lead to a reboot with euphoria work fine with aosp and nameless. Euphoria is fast, faster than nameless, which would be fast enough for me. There are no problems which exist with every ROM.
Does anyone have a recommendation for a ROM for the P880 which works without big problems. At the moment I think about to go back to 4.4 and try beanstalk-4.4.4010-20140904-p880cm
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
lg-optimus said:
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showpost.php?p=66049970&postcount=1195
This is the latest 5.1.1 ROM with security patch level at 2016-04-01. It has all known stagefright bugs fixed so far.
If you wish to report issues on the ROM I shared, then use the thread over there, not here.
MoltenMotherBoard is the last custom ROM that I miss to test. I'm going to try it in the next days.
According to my test, my answer to the thread question is: NO, there's no custom rom working fine for my daily use.
Actually fastest rom was liquid smooth 4.4.4. Our phone hardware outdated. Like the others said this phone is crap
I'm running Euphoria version 1.0-p880-20150130 (Android 5.0.2), it's the best Lollipop based custom ROM for our device in my opinion. Unlike AOSP it has more settings (& features), and it's more stable than later versions of Euphoria. If you want to stick to KitKat, check out the latest CM nightlies.
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
bs360 said:
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
Click to expand...
Click to collapse
having JellyBean running on your device in 2016 is a very very very bad idea.
Here's the issues I found with LG stock JB-4.1.2 ROM v20 euro-open. If you can live with them, then good for you.
- Bluetooth button action broken. Cannot invoke Google Search or Voice Dialer from bluetooth headsets. Fixed in custom ROM such as CM/AOSP KK and LP.
- No update for Google Maps. Version 7 is the final version for v20c. Fixed in CM/AOSP KK/LP.
- No notification from Lock Screen. Fixed in CM/AOSP LP.
- No smart lock to avoid the hassle of entering PINs for known location and known BT device. Fixed in CM/AOSP LP.
- No screen cast. Fixed in AOSP LP.
- No bluetooth tethering. Fixed in AOSP LP.
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
But yes, you're right...I'm ok because for instance I don't use bluetooth at all.
I still miss to test "AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock? Are these working ? camera, flash, barcode, dialer reader, calls in general..
thanks in advance
bs360 said:
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
"AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock?
Click to expand...
Click to collapse
When I was still on LG stock JB, Maps somehow got updated. But then the device slowed to crawl and I factory reset it and I didn't get Google Play store to update it again. Glad you have it and it works for you.
Barcode and FM radio are not working. If these 2 are important to you, then you should stick with LG stock.
For UI smoothness, I think Lollipop itself has made tons of improvement that it is at least the same or better than JB. Don't take my words for it, you should try it out yourself and pass on the judgement.
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
asgz said:
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
Click to expand...
Click to collapse
please link?
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
asgz said:
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
Click to expand...
Click to collapse
i just get an loop bot, i can't install a kernel..
Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6
This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.
I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.
I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse
Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck
Hey guys, since I've installed CM14.1 I'm been facing a lot of issues and bugs with the gallery app, the camera app & many times I get a notification that "CM bug report not working" and my phone becomes unresponsive. Which ROM would you guys suggest would be the best alternative to CM14.1? Or should I roll back to stock AOSP 6.0 Marshmallow?
EDIT: I'm really confused which ROM should I switch to I really wanna try MIUI 8 for TITAN and also lineage OS. I want no bugs that would be good because I really don't get the time to reflash other ROM's and keep testing others. So please suggest the one which has almost NO BUGS.
Try this stable af, just a couple of minor bugs here & there but the rom overall is fluid & battery efficient as heck.
rootb3r said:
Hey guys, since I've installed CM14.1 I'm been facing a lot of issues and bugs with the gallery app, the camera app & many times I get a notification that "CM bug report not working" and my phone becomes unresponsive. Which ROM would you guys suggest would be best alternative to CM14.1? Or should I roll back to stock AOSP 6.0 Marshmallow?
Click to expand...
Click to collapse
You might be running an really old build, since those issues were long solved. CM is dead now, but there's LineageOS, its sucessor. If you want, download it here.
I am looking for a non-stock rom that has pretty much everything working. I have tried many, and the one that worked the best was CM 13.0 by HDHR. It was very smooth and I liked it's features like hold volume buttons to skip music and the ability to use themes, but I've had issues with the gallery. Some thumbnails for photos or videos would not show up and after trying to inspect them, everything in the gallery would just turn black and I had to restart the app. Someone recommended using a media scanner app but that didn't do a thing . I had the same issue on PAC rom by aswinp222 and lineage os 13 by HDHR. I have also tried lineage os 14 by Rohan Taneja, but it had many bugs including not being able to move apps to internal memory. I am currently on the stock rom, because every rom I tried so far had a bug that made me change it to another.
tl;dr
I need a recommendation on a good rom that has almost no bugs and is not the stock one.
I have tried CM 13.0, PAC rom, androium 7, lineage 13 and 14, but none are bug free.
The touch delay is present since the release of Marshmallow, Nougat and Oreo ROMs in Titan (not sure about Falcon). There is no escape. It's good to see our 2014 devices with the latest version of the Android, but this error is very annoying and is being ignored. Doesn't matter how good the ROM is. If you using any custom ROM with Android 6.0 and up on titan, i'm sure you have this issue.
So i want to open a discussion about this issue here
If you don't know what i talking about, let's simulate the issue:
Try to write something in stock keyboard of your MM,Nougat or Oreo ROM. Now try pressing a second finger in the screen out of the keyboard and write anything else... You noticed? No?
Try to play a very intensive tap game, like Geometry Dash. Play a bit. Now play with a second finger on screen... You noticed?
Only KitKat and Lollipop Roms are free from this bug.
So, the only workaround for this touch delay is pressing a second finger on screen. Shame.
The questions left: Anyone knows a solution? The cause of this issue? There is no way to fix this?
I tried some custom kernels, no success.
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Metalhead666 said:
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Click to expand...
Click to collapse
Some people say the same on Lenovo Foruns...
Pixx 1001 said:
Some people say the same on Lenovo Foruns...
Click to expand...
Click to collapse
I think it is a kernel related issue rather than the bootloader,like some people said on lenovo foruns.I don't have proper knowledge to fix it,you could try to contact some of our developers,maybe there's still someone interested.
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
HiR3x said:
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
Click to expand...
Click to collapse
Every single ROM above 6.0 that I tested have this problem (Cm,AOKP,AOSP,Lineage,Slim,DU,CypherOS,AEX,CrDroid,RR and many more),with and without custom kernels.
I don't use my Moto G to play games , but some random games from PlayStore (Minigore 2, Bejeweled 2, Samurai II) the touch doesn't work well (or simply doesn't work! You can test all of them if you want). Using a 5.1 ROM, they work normally. It would be nice if the people post more problems about this touch issue happening on apps/games on Moto G Titan. I want to know if the same happens on Moto G Falcon, 4G variants.
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Jimisballjohn said:
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Click to expand...
Click to collapse
Well, I used ViperOs (7.1) as my daily driver at work, school for a good time (6 months I guess)... I liked Nougat Features and I guess I will keep using it, or another Nougat ROM, as they work perfectly for it on Titan.
Looks like titan Pie ROMs have the issue too (Used LineageOS 16 for testing).
It sucks that this still has not been resolved. Happened to me as well on LineageOS 16.
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
LightWard said:
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
Click to expand...
Click to collapse
I would like to test it myself and give a feedback, but sadly, my old Moto G2 had the input of the charger/usb connector broken. If anyone have tested the ROM too, would be good if they give a feedback here.