[ROM][UNOFFICIAL] CyanogenMod 12 Nightly Builds / OpenDesireProject

[CybermindOff]

on/off "use NuPlayer" does not solve the problem, at least for me

 

[dimitrioos]

on/off "use NuPlayer" does not solve the problem, at least for me

Yeah, I see it now, thanks. I've switched back to the NuPlayer, ringtone didn't work for the first time but then works. Seems that the problem is intermittent and probably not related to NuPlayer itself.

 

[pokornyja]

NoRingtone Solution

on/off "use NuPlayer" does not solve the problem, at least for me

Hi all, there is a beta solution....
1. Set your own MP3 as a ringtone
2. Reboot/turn Off Device
3. Remove battery (20+ sec)
4. Turn on device.
5. And now second call ring, for me... I don't know why First call didn't ring....

---------- Post added at 01:12 PM ---------- Previous post was at 01:04 PM ----------

Hi all, there is a beta solution....
1. Set your own MP3 as a ringtone
2. Reboot/turn Off Device
3. Remove battery (20+ sec)
4. Turn on device.
5. And every second call ring, for me... I don't know why First call didn't ring....

6. Any ideas? :/

 

[holdonL]

gapps

Guys, can you provide me with a link of gapps that work fine for latest build? Thx

---------- Post added at 05:13 PM ---------- Previous post was at 04:15 PM ----------

Hi! whether new build ... would like to correct the first mic!
New report about flash last build:
After install GAPPS!!!:
work:
1. home button
2. work quicke options
3. keyboard
4. block screen
5. adb
6. gps
7. wi-fi
8. clock widget
9. rotate screen
10. systems sound and vibro
not work:
1. main and front camera
2. switch usb plugin to PC
3. mic in call
4. sound incoming call
5. same freezzz in system
until all that is found!

how did you manage to install gapps?

 

[ralfbergs]

how did you manage to install gapps?

I used the GApps minimal-edition referenced on the following page: http://forum.xda-developers.com/showpost.php?p=57195273&postcount=46

 

[holdonL]

I used the GApps minimal-edition referenced on the following page: http://forum.xda-developers.com/showpost.php?p=57195273&postcount=46

already tried it

 

[dimitrioos]

already tried it

I guess, you had previously tried Gapps-full. If so, there is no more free space in your /system partition (actually, this is the reason why Gapps-full do not work and Gapps-mini won't install too). Then you have two options now:
1. Less lossy, more hacky: go to /system/app/ and remove heaviest apps that exist in Gapps-full.zip/system/app. These are Maps, Gmail2, GmsCore, GoogleTTS, some other
2. Simpler: wipe system, reinstall CM12 and Gapps-mini.

Hope this helps.

 

[holdonL]

I guess, you had previously tried Gapps-full. If so, there is no more free space in your /system partition (actually, this is the reason why Gapps-full do not work and Gapps-mini won't install too). Then you have two options now:
1. Less lossy, more hacky: go to /system/app/ and remove heaviest apps that exist in Gapps-full.zip/system/app. These are Maps, Gmail2, GmsCore, GoogleTTS, some other
2. Simpler: wipe system, reinstall CM12 and Gapps-mini.

Hope this helps.

nope, reinstalled rom and gapps. still doesnt work

 

[docertabum]

guys, could somebody please post a file related to touch screen? I am at work and cant download another build. Thank you!

 

[Lapyyyyyy]

guys, could somebody please post a file related to touch screen? I am at work and cant download another build. Thank you!

View attachment atmel-touchscreen.kl.zip

 

[docertabum]

attached is the file (from cm11) as a temporary solution to have a normally working touch screen (no more circle cursor). It's not a zip so please before applying the file remove false postfix. Put the file into /system/usr/idc. Also set proper permissions.

 

[ralfbergs]

How to reach substantial progress in development of this FW?

@kylon and all:

As I'm new to this forum here and unfamiliar with how you do development, may I ask how you track issues re. FW drops you released?

I would really love to see some substantial progress on the quality of this FW, as I'm intrigued by the power you can inflate to such an old device by upgrading it to Lollipop.

I'm willing to spend some time doing testing and QA, please let me know how I could help...

Best,

Ralf

 

[ArchithV]

Keeps rebooting

Hello Devs,

I followed all the instructions and installed the ROM after doing a factory reset using TWRP 2.8 and also replaced the files that are listed in the previous posts so as to fix touch screen,home button and keyboard issues and flashed boot.img using fastboot. However, after installing, the phone boots and immediately I get the dreaded 'process com.android.phone has stopped' error and then it reboots again. This keeps happening. Any solutions? Please help me out! :crying:

@kylon any tips?

 

[pokornyja]

Hello Devs,

I followed all the instructions and installed the ROM after doing a factory reset using TWRP 2.8 and also replaced the files that are listed in the previous posts so as to fix touch screen,home button and keyboard issues and flashed boot.img using fastboot. However, after installing, the phone boots and immediately I get the dreaded 'process com.android.phone has stopped' error and then it reboots again. This keeps happening. Any solutions? Please help me out! :crying:

@kylon any tips?

Hi, try to install Gapps, before firts boot.

 

[kylon]

@kylon and all:

As I'm new to this forum here and unfamiliar with how you do development, may I ask how you track issues re. FW drops you released?

I would really love to see some substantial progress on the quality of this FW, as I'm intrigued by the power you can inflate to such an old device by upgrading it to Lollipop.

I'm willing to spend some time doing testing and QA, please let me know how I could help...

Best,

Ralf

by reading yours posts.

you can test the rom or you can try to fix bugs
if you encounter a bug and you are sure that is not caused by an app or something you did, take a log.

Hello Devs,

I followed all the instructions and installed the ROM after doing a factory reset using TWRP 2.8 and also replaced the files that are listed in the previous posts so as to fix touch screen,home button and keyboard issues and flashed boot.img using fastboot. However, after installing, the phone boots and immediately I get the dreaded 'process com.android.phone has stopped' error and then it reboots again. This keeps happening. Any solutions? Please help me out! :crying:

@kylon any tips?

try the next build or try a clean install (no gapps or any other zip)

 

[ralfbergs]

by reading yours posts.

you can test the rom or you can try to fix bugs
if you encounter a bug and you are sure that is not caused by an app or something you did, take a log.



try the next build or try a clean install (no gapps or any other zip)

I did already quite some testing of the DEC-04 build. Here's the issues I noticed:

• Phone is somehow regarded as a tablet by the Android OS.
• Front camera not working. I thought I had seen it working once, but maybe I’m confused. Anyway, as of now the front camera seems not to be detected/functioning.
• I replaced some of the apps in the apps dock with apps I installed from Google Play. Some of these apps will disappear after a reboot. When I noticed this and wanted to put them back by opening the apps drawer I observed that Android was currently populating/updating the apps drawer with some still missing apps. But even after it had finished showing all installed apps in the app drawer the apps dock was still missing some apps. So I dragged them back from the drawer onto the dock. Again, after a reboot they will be gone again.
• Speed of cellular data connections seems slow. Unfortunately I couldn’t verify whether the cellular network settings are ok, since every time I tried to enter one of the corresponding Settings menu item the process com.android.phone would crash (with the effect that I had to re-enter my SIM PIN and also the screenlock PIN).
• Later I tried it again, and this time it didn’t crash. All the settings were fine, so I wonder whether there is a problem with regards to the modem firmware?
• Update 2014-12-11: Connecting the charger when the phone is powered down will cause it to boot into the TWRP recovery system.
• Trying to open menu item Wireless & Networks > Cellular networks > Carrier Settings might cause process com.android.media to stop.
• Ringtone will be quiet on incoming calls.
• Microphone will be muted (or not properly amplified) when the first outbound(!) call takes place (in non-speakerphone mode). After you have gone on speakerphone and back, the microphone will then be working.
• Moving apps to the external SD card is unreliable. Often it doesn’t work without any indication as to why. If you then repeat it again it may actually work.

Unfortunately I'm not an Android programmer, so I can't actively fix issues myself.

Can you please point me to how to further investigate the above issues? How would I take logs? Is it about "adb logcat"? Do I have to increase the logging level, if yes, how?

Kind regards,

Ralf

 

[lgv2800]

Help with touch screen and home button

Hello. Which permission does i need to use? I tried with rw -r -r but i still get the circel and no normal touch screen input. I tried to put the right files in the right places with ES file explorer as i am having root. I copy everything and when i reboot there is still a circel on the screen and no normal touch screen nor working home button. Please help me.

 

[kylon]

New build up

 

[holdonL]

Hello. Which permission does i need to use? I tried with rw -r -r but i still get the circel and no normal touch screen input. I tried to put the right files in the right places with ES file explorer as i am having root. I copy everything and when i reboot there is still a circel on the screen and no normal touch screen nor working home button. Please help me.

Man, you need to place this file to a rom then flash it.

---------- Post added at 08:14 PM ---------- Previous post was at 08:09 PM ----------

New build up

Can you advise something to make gapps work?

 

[ralfbergs]

Man, you need to place this file to a rom then flash it.

No. I copied it into the filesystem using

adb push

and that did the trick. It's just a config file for the screen driver, obviously...