Database Develop

What is the CM9 issues and how do you guys survive with it ?

Hi , anyone can tell me the exact CM9 issues and why it's cannot be fixed yet ?
So how you guys survive with that ROM ?
Please share me some TIPS .
Currently i'm using Stock Gingerbread since I bought it last year December and now I would like to use CM9 custom rom (PARANOIDANDROID) yayyy
Thanks .

reyyy96 said:
Hi , anyone can tell me the exact CM9 issues and why it's cannot be fixed yet ?
So how you guys survive with that ROM ?
Please share me some TIPS .
Currently i'm using Stock Gingerbread since I bought it last year December and now I would like to use CM9 custom rom (PARANOIDANDROID) yayyy
Thanks .
Click to expand...
Click to collapse
I guess the idea is to test your own skills in modding your phone and see, what the different developers would like us to have. After a few installs, you are hooked at getting your daily fix of new ROM and will suffer withdrawal symptoms, if no new ROM are a available for even a short period!!
Even if all the latest ROMs are not fully functional, they still add many new features to our phone.
I have become very enthusiastic about my phone again and I have had it for almost two years now. The longest time I have ever had a mobile phone.
What also is interesting is that you are able to try so many new apps, that only works if your phone is rooted.
So the benefits are many and if you are not satisfied, there are very good guides on how to go back to stock.
Good luck

reyyy96 said:
Hi , anyone can tell me the exact CM9 issues and why it's cannot be fixed yet ?
So how you guys survive with that ROM ?
Please share me some TIPS .
Currently i'm using Stock Gingerbread since I bought it last year December and now I would like to use CM9 custom rom (PARANOIDANDROID) yayyy
Thanks .
Click to expand...
Click to collapse
CM 9 don't support Hardware acceleration. Thats the major problem that i know

reyyy96 said:
Hi , anyone can tell me the exact CM9 issues and why it's cannot be fixed yet ?
So how you guys survive with that ROM ?
Please share me some TIPS .
Currently i'm using Stock Gingerbread since I bought it last year December and now I would like to use CM9 custom rom (PARANOIDANDROID) yayyy
Thanks .
Click to expand...
Click to collapse
Hardware Acceleration in CM9 for LG O2X is not working as of now (Needs LG to release an ICS based kernel).
Due to which:
- Video Recording doesn't work.
- Will not be able to play HD videos.
- Some of the system apps will start to lag after some usage (Phone & Contacts).

thank you . i hope the promised official ICS update will reach soon .

reyyy96 said:
Hi , anyone can tell me the exact CM9 issues and why it's cannot be fixed yet ?
So how you guys survive with that ROM ?
Please share me some TIPS .
Currently i'm using Stock Gingerbread since I bought it last year December and now I would like to use CM9 custom rom (PARANOIDANDROID) yayyy
Thanks .
Click to expand...
Click to collapse
Ok, so CM 9 and CM 10 has the following problems:
1) No Hardware acceleration which means:
a) You CAN'T use your video camera at all. Now, I know that some says that you can use Videocam illusion, but that app can record only very low quality videos, which I found to be pretty useless (a lot of CPU use for that low quality).
b) Google Chrome is not supported due to it's need to access the GPU, but this is not so important due to other very good browsers
c) You will experience scrolling jittering. That being said when you will try to change between photos in the gallery (usually there is the bigest problem), or between songs in some media players by swaping on the screen, you will see something like the photo or album art is going back from where it came, but the result is good: changing the photo / song. The only problem is the visual one.
d) Gameloft games, and especially those with a little video at the begining will not work until you delete those clips from the instalation folder.
2) No radio application => no more FM radio for you. Wi-Fi (or a really well data plan) resolves this thing by using it for Tune-in Radio, a very good application for radio. I prefer to use it even on GB roms, because of the very good sound quality regardless the standard radio that sometimes loses the signal.
3) On CM 10 there are a few more bugs like no automatic brightness, or battery drain due to Wi-fi. Regardless all theese bugs, I found CM 10 from ParanoidAndroid to be a way much better rom than any other around here. Keeping the Wi-Fi off I don't experience any battery drain (more than that my battery last longer than anytime) and my favorite no data connection lost (I don't know if this was a carrier problem or not, but before switching to CM 10 i had a lot of data connection problems).
4) Not to be forgotten the lag on installing applications from Google Play Store. I found this problem on almost every single rom I've tried, and I tried almost all of them. I think I found only one or two roms w/o this problem, but being a maniac for the latest updates I've chosen the ICS and JB roms instead of a very stable one
5) No GPS working on CM 10
Now it's your decision. If you can live w/o video camera and gps and try to not get angry at every scroll bug you should really try the new CM 9 and 10 roms

al3x1393 said:
5) No GPS working on CM 10
Click to expand...
Click to collapse
GPS is working fine for me on CM10 (KashaMalaga's build)
reyyy96 said:
So how you guys survive with that ROM ?
Click to expand...
Click to collapse
I know this may sound weird to you, but: I can survive without any ROM.
It's not that your life depends on your smartphone, does it?
Just be happy with what you got.

Confused with Lollipop builds! Please help me select..

Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.

Bump..

abhi.eternal said:
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Click to expand...
Click to collapse
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.

@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.

Tripple-c said:
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
Click to expand...
Click to collapse
That issue you discribed above would only happen if you did a dirty install and didn't install gapps. The newer version backs up gapps so you only have to install. I recommend a clean install(factory reset and format system) to get the camera to detect the only way and then reinstall with gapps use the newest nightly.

abhi.eternal said:
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Click to expand...
Click to collapse
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.

pekcle said:
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
Click to expand...
Click to collapse
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated

abhi.eternal said:
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
Click to expand...
Click to collapse
It's all cool. There's no harm in that. But Android 4.1 to 4.4 was fairly mild and incremental. Lollipop was a hefty change in concept and usage. I tried it on my N7 2013, and it was just harder to use. Buttons were smaller and closer together, more taps and swipes just to do something, etc. It feels like they compromised ease of use just to adhere to the material design. Seriously made me consider going to an Apple product. No joke!

CyanogenMod 12 fix for android auto?

For some reason, I cannot select ok and continue on my pioneer 4100 after I connect to USB. I'm using cm12 with note 4.

Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).

diagdave said:
Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).
Click to expand...
Click to collapse
Yes, so downgrading fix the problem.
Thanks 4 the response.

killa2009 said:
Yes, so downgrading fix the problem.
Thanks 4 the response.
Click to expand...
Click to collapse
Yep, the layout was screwed on 5.1. if you force your dpi on your phone to 120 it works - of course your phone then is almost useless. so downgrade was only option.

So when do think there will be a fix? Can I force phone dpi to 120 then change it back normal after I select the box?

I have the save problem but it is intermittent. On 5.02. Thanks for the info. I thought my micro bypass was bad.

For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy

akp982 said:
For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy
Click to expand...
Click to collapse
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...

s2kpdx said:
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...
Click to expand...
Click to collapse
Since I could not get the CM from before 5/22 from CM I went on a hunt today to find a rom that would work with my 4100nex, I found that Euphoria from 6/02 based on 5.1.1 works for me. I tried several other builds from different devs, I really wanted to be able to find a 5.1.x that worked and it appears I have. I was not able to get past the Don't Show me this again scrunched up screen / DPI issue. I still have a phone book issue that I had on CM 12, for some reason it will not show names in my call log, but at least I got back into Android Auto. Hope this helps someone.

The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.

bmxchampga said:
The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.
Click to expand...
Click to collapse
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.

WisdomWolf said:
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.
Click to expand...
Click to collapse
Yeah, I just updated to the latest nightly and it broke Auto for me again.

how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)

arabcamel said:
how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)
Click to expand...
Click to collapse
Some phones have a better selection of older releases than others: http://download.cyanogenmod.org/
Sometimes other releases are downloadable from elsewhere.
Sometimes people keep copies under /sdcard/cmupdater.

This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal

Awesome, I'll have to flash and try myself. Do you think this would also apply to other custom ROMs that are based off of the newest CM?
Sent from my A0001 using XDA Free mobile app

akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
Click to expand...
Click to collapse
Some insight posted there:
density: do not apply to virtual displays Check the incoming configuration density to ensure that it is the same as the device's default density before forcing preferred values. Only apply display metrics if the display is not a presentation.
Click to expand...
Click to collapse
I was able to work around this problem on my Xperia Z2 tablet w/ CM12.1 by lowering ro.sf.lcd.density in /system/build.prop from default 240 to 180.
But this is just a workaround for the REAL problem shown in the comment. It had the side effect of making icons on homescreen smaller.
The REAL problem is that Android Auto uses a virtual display/Presentation to make up the AA display. Some ROMs were applying physical screen DPI of the phone to the virtual display, instead of the AA specified parameters that should come from the headunit. For Pioneer HUs (or at least 4100NEX) the parameters are 800x480 with a reported DPI of 160.

akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal
Click to expand...
Click to collapse
Flashed July 4th build of BlissPop and it works great now with Android Auto. I had to turn off ADB in the developer settings.

Clean install or dirty...ota

Question Android auto problems

I get some trouble with my 11 and android auto on uconnect 7 fca. The phone normally connects to to connect with aa, but after a phone calling, the audio (spotify ecc), start to hear from the phone speaker and not from the car speakers. Tried everything but no success.

got the same issue

Tried everything without success

What rom are yours?
I have the same problem, with Global EEA ROM.
Waiting 3 more days to unlock and flash xiaomi.eu. Hope it will solve the issue.

I confirm - xiaomi.eu weekly rom fixed the issue..

Is there any other solution.
I have MIUI 12.5.9 global and this problem persist.

forgotten_jp said:
Is there any other solution.
I have MIUI 12.5.9 global and this problem persist.
Click to expand...
Click to collapse
Hm.. .9? I just got an update here of MIUI Global 12.5.7 and thought that was the latest. I still have the same problem though So annoying that I went back to an really old huawei phone instead.

Me too same issue, each time a firmware update comes I test it and I pray they fixed that annoying issue without any success. This issue is been since the day one I got the phone. This is sad since my old Oneplus 6 works just fine :/

The only way i find to resolve this problem was unlock bootloader and flash another rom, in my case One OS. :/

JuanSebastianG said:
The only way i find to resolve this problem was unlock bootloader and flash another rom, in my case One OS. :/
Click to expand...
Click to collapse
How is that rom otherwise compared to the Global rom?

I've spoke to some people of Xiaomi forums and the admin over there is claiming AA is broken not just on Xiaomi but also other phones and that is an Android 11 problem that was not resolved yet on Android open source project, not sure if that is true as I don't have another phone on Android 11 to test.
I've already opened a ticket with Xiaomi for that, several months ago. Still no updates on it. If someone has any other android 11 phone that is not xiaomi and could test to confirm it would be great!

Mephisto_POA said:
I've spoke to some people of Xiaomi forums and the admin over there is claiming AA is broken not just on Xiaomi but also other phones and that is an Android 11 problem that was not resolved yet on Android open source project, not sure if that is true as I don't have another phone on Android 11 to test.
I've already opened a ticket with Xiaomi for that, several months ago. Still no updates on it. If someone has any other android 11 phone that is not xiaomi and could test to confirm it would be great!
Click to expand...
Click to collapse
As I understand there was an Android 11 problem that is solved. I have talked to people using andoid 11 on Oneplus devices that works fine they claim.

I have the problem only with Waze. After a phone call, Waze is hearing from the phone speaker. The rest of the apps working ok. It's a Skoda...
I had some problem also with Samsung Note 10 before and it was the same problem with Waze app but not on every phone call. Let's say 3 from 5.

General New update 36.9.7

Today auto installed 36.9.7
Vivo quicly patched bugs of 36.9.6 which was having a major Call notification issues.
Let me know your opinions.

no update available till now.
India. FunTouch OS 12

In INDIA, Bengaluru, it was updated around 11.30 in the monring.

no updates yet

I got the update today.
It seems to have reinstalled Jovi Voice which I had removed before using ADB.
Other than that it seems to be working as normal.

I have imported India version with FunTouch OS 12. Got the latest update too.
The phone seems to be working very well.
The only issue I have since I got the phone is when adding card to google pay contactless payament cannot be activated. I do not have loacation resrictions using gpay and with my other phones gpay contacltless payment can be activated successfully. My vivo is not rooted and runs factory rom.
Do yoy people from India have the same issue with gpay contactless payment?
thanks

gpx said:
I have imported India version with FunTouch OS 12. Got the latest update too.
The phone seems to be working very well.
The only issue I have since I got the phone is when adding card to google pay contactless payament cannot be activated. I do not have loacation resrictions using gpay and with my other phones gpay contacltless payment can be activated successfully. My vivo is not rooted and runs factory rom.
Do yoy people from India have the same issue with gpay contactless payment?
thanks
Click to expand...
Click to collapse
In India I have not tired this option, to work this properly you need to enable NFC in phone. In india lot of hackers are waiting to snipoff your wallet and i do not have RFID blocking wallet.

Received Origin OS update PD2145B_A_5.13.12

fabrixx said:
Received Origin OS update PD2145B_A_5.13.12
Click to expand...
Click to collapse
Super. But in India it is FUNTOUH OS.

Got the update, the T* coating bug is fixed YAAAY!
everything is normal.

grex_vibra said:
Got the update, the T* coating bug is fixed YAAAY!
everything is normal.
Click to expand...
Click to collapse
Nice to here. Vivo is taking actions hard and fast, But still we should not get these bugs in Flagship modules.

Bringing out the scam companies like Samsung, Vivo are doing. Am using Vivo X70 pro plus. Recently I updated my software OTA push to 36.9.7 (from 36.8.) but took a camera sample before update. Immediately after update took another sample i matter of 15 min gap. There was hell lot of downgrade. Plus other bugs impacting day to day usage. Wanted your help to voice this out. Below are the identified issues beimg faced.
1. Camera quality is greatly downgraded
2. Background apps getting auto closed like Nova Launcher, SD Maid, Accu battery, etc. Thus accessibility service also not working linked to these apps as tgey are automatically getting off. This was not there before the update.
3. Amazon app is getting auto closed at payment selection page every time thus amazon app now not useful.
Attaching unaltered image sample before & after update.
3.3 mb is the one before update
3.5 mb one is post update (see tubelight & flower design on the matress, etc)
Can someone guide me on how to voice tjis to Vivo. This is malpractice as I suspect deliberate downgrade of camera & other bugs.

I dont see a downgrade or a difference at all here.

Killuminati91 said:
I dont see a downgrade or a difference at all here.
Click to expand...
Click to collapse
Look at the light, in post update image its bit spread, less t star
Also if you compare flower images on the left, you will clearly see that new images has distorted details clearly evident