[ROM][v500][UNOFFICIAL] CyanogenMod 12.1 [20151124]

[dirlan2001]

Hi all,

Something I couldn't find an answer to : can I dirty flash this ROM on top of the AOSP from this thread ? Or do I act as if I come from stock ?

Cheers

 

[Deltadroid]

Hi all,

Something I couldn't find an answer to : can I dirty flash this ROM on top of the AOSP from this thread ? Or do I act as if I come from stock ?

Cheers

A factory reset is always recommended when switching ROMs that have different source code bases.

Yes, you should factory reset if coming from AOSP.

 

[dirlan2001]

A factory reset is always recommended when switching ROMs that have different source code bases.

Yes, you should factory reset if coming from AOSP.

Tnx for the quick reply. In between I found that both ROMS are almost identical, no much need for switching for now...

Cheers

 

[fefifofum]

New build released

with upstream changes.

 

[Cal]

Had one unusual issue when overwriting this new ROM update...and that was on reboot. When the "starting apps" screen appeared, that process 'hung'. Had to hold the power button until the system restarted...then all is fine. First time thats happened.

Question: Screen is set default @ 320ppi. Why so high? I set to 300ppi & can tell no difference. Isn't the factory resolution set much lower?

 

[Deltadroid]

Had one unusual issue when overwriting this new ROM update...and that was on reboot. When the "starting apps" screen appeared, that process 'hung'. Had to hold the power button until the system restarted...then all is fine. First time thats happened.

Question: Screen is set default @ 320ppi. Why so high? I set to 300ppi & can tell no difference. Isn't the factory resolution set much lower?

changing the DPI in build.prop will also affect which version the play store installs and which version of Google play services is installed by gapps base package.

 

[Cal]

changing the DPI in build.prop will also affect which version the play store installs and which version of Google play services is installed by gapps base package.

Now I am a bit confused. In the description of the LG 500 Tab 8.3 - it lists a ppi or pixel density of 273ppi.
Have most ROMS changed this now? Also, after installing and running a play store with different specs...how does that affect the display and also the play store? Mind explaining it a bit more.

Thank you.

 

[Deltadroid]

Now I am a bit confused. In the description of the LG 500 Tab 8.3 - it lists a ppi or pixel density of 273ppi.
Have most ROMS changed this now? Also, after installing and running a play store with different specs...how does that affect the display and also the play store? Mind explaining it a bit more.

Thank you.

If ro.sf.lcd_density is changed in build.prop, then it will affect play store's choice of dpi specific apps. Also, which version of play services is installed by gapps base packages.

 

[Cal]

So, Deltandroid, the dpi or ppi have been modified for some time (to a higher density that the initial one from factory) and that has affected the Play Store versions that are installed?
That is interesting...how may versions of Play Store would you say are influenced by dpi? And is that the only limitation to installing a different version of Play Store, or could be be best to not install any Play Store apps as Fefifofum indicated in another post?

I know this is asking a lot of you...but could you explain a bit about this in detail?

Many thanks!

 

[Deltadroid]

So, Deltandroid, the dpi or ppi have been modified for some time (to a higher density that the initial one from factory) and that has affected the Play Store versions that are installed?
That is interesting...how may versions of Play Store would you say are influenced by dpi? And is that the only limitation to installing a different version of Play Store, or could be be best to not install any Play Store apps as Fefifofum indicated in another post?

I know this is asking a lot of you...but could you explain a bit about this in detail?

Many thanks!

other factors besides dpi can affect version numbers, but dpi is the most common one. about half of the gapps versions are affected by dpi in build.prop.

Although, cm has a way of changing dpi in the settings that won't affect play store. (settings --> display --> lcd density)

 

[pnin]

FTR, I just saw the an occurrence of a spontaneous SDcard unmount on my device sporting the latest version of this ROM -- logs sent privately...

EDIT: this may be totally unrelated (I haven't really looked into it but I've tried every procedure I know), but after upgrading I'm having trouble reinstalling Viper4Android -- it was working perfectly before...

Tapatalked from my V500

 

[luisbraz]

Latest release is working ok with latest xposed official v75.

 

[Deltadroid]

I just wanted to mention that since a few days ago, my tablet started to show those "sdcard unmount" messages on the screen every time I would wake the device from sleep mode. I started to investigate the files on my sdcard to see if I could figure out what was causing the sdcard to unmount. I then removed a directory that contained a large amount of zip files, and after that, I have not had any "sdcard unmount" messages since.

So, maybe most of those sdcard unmount issues are caused by corrupted files on the sdcard that hang the system.

 

[giovaorama]

This morning i had a really strange behavior.

In background it was installing facebook. As usual this takes a lot and then i open something else.

I run google + and after a swype to update, it forces close and then i start to get force close notifications for every running (?) app even nova launcher.

Each time i click ok in the notification a new one comes.

I had to reboot.

Any idea? If this happens again does a logcat after reboot will be useful? I think no.

Regarding the sd unmounts. For me these are very random. I don't actually use the sd, it just contains movie for my daughter to have something to see when we are in holiday.
Just to say that i (theoretically) never access the sd.
Maybe there is some process that automatically access to sd filesystem and has some problems with "strange" folder or semi corrupted filesystem.

Inviato dal mio LG-V500 utilizzando Tapatalk

 

[Cal]

@ Deltandroid ~ Sdcard dismounts

@ Deltandroid said in post #473: <snipped> "I then removed a directory that contained a large amount of zip files, and after that, I have not had any "sdcard unmount" messages since.
So, maybe most of those sdcard unmount issues are caused by corrupted files on the sdcard that hang the system."

I have a 8GB card...I have *never* had the storage card dismount, and I have had literally everything on that card...bad hacked APKs to bad Roms. Cheap 8GB card too! So it is something else IMO.

 

[fefifofum]

New build released

with minor changes: added initial camera wrapper, disable no_sleep in mpdecision and don't switch to BFQ IO scheduler until boot is complete.

 

[juniorhxcx]

I'm using the Exodus ROM, it is very fast!Only I started having the problem by disconnecting the MicroSD (only when I move applications to the MicroSD). If you leave the internal memory is very rare to it.

Another problem I'm having is the issue of Date and Time. Inporta not to let time automatically by the network or manual, to shut down or restart the tablet time is unset.

I wonder if the current CM has corrected the problem of MicroSd and has some other bug?

For the Exodus is based on the CM, but I hope that the CM has not these errors ^^.

 

[Deltadroid]

@fefifofum

On the stock lollipop ROM, there are some settings in WCNSS_qcom_cfg.ini that fix the Wi-Fi so that it can connect to channels above 11.

The Wi-Fi settings in this rom are hard coded to this:
gStaCountryCode=BR

The stock ROM must also enable this setting to match the above setting:
gCrdaDefaultCountryCode=BR

The problem with some routers could be that both these settings must be enabled and set to the same country code.

 

[fishears]

@fefifofum

On the stock lollipop ROM, there are some settings in WCNSS_qcom_cfg.ini that fix the Wi-Fi so that it can connect to channels above 11.

The Wi-Fi settings in this rom are hard coded to this:
gStaCountryCode=BR

The stock ROM must also enable this setting to match the above setting:
gCrdaDefaultCountryCode=BR

The problem with some routers could be that both these settings must be enabled and set to the same country code.

It's actually "gCRDAfaultCountryCode" and I'm pretty sure they don't have to be the same but this particular key is responsible for deciding what channels are available to you so you could change it if you travel to another country. Just make sure you set it to a country code that uses the channels you want. For me, I use "GB" to give me channels 1-13 but if I visit Japan I can change it to "JP" and get channels 1-14 for example.

 

[Deltadroid]

It's actually "gCRDAfaultCountryCode"

strange, not on this rom.