[Q&A] [ROM][YUGA][LP][5.0.1] CyanogenMod 12 Unofficial [NIGHTLY BUILDS]

pmkscorpio

Member
Aug 28, 2012
17
3
0
CHENNAI
First of all sorry for that. Actually the old build was on the top and I installed it.

Now I changed it and it is working fine now..

Thank you

Sent from my Xperia Z using XDA Free mobile app
 

mostafaz

Senior Member
Mar 16, 2013
1,216
2,076
153
iran
Thanks
I'd flashed 15 march and some problem fixed _ just flashed and cache n dalvik clean
Also a few days ago at first installations flashed bundled boot.IMG
But these issue remained :
1_Assigned mp3 ringtone changed to default at next boot
2_wlan indicates always on in battery usage even if turned off
3_user photo doesn't add / just name changed
...
I think u want keep it clean and simple as source
Can u add some features to kernel : CPU GPU I/O to have lower freq and batt usage?
Regards
 

EdeNBaruch

Member
Sep 24, 2013
49
0
0
24
After the last update, when the notification "toast" come, Nothing happends when I click on it, but I can swype it away.
Please, fix.
Also: I can't talk on speaker phone :(, They hear the background noises but me.
 

omarsss98

New member
Dec 18, 2014
3
0
0
I need help

what i do with this ?
cm-12-20150320-INFECTED-yuga.zip.md5sum :confused:

and when i flash the rom via rcovery nothing happen just installing and never finish
i lose my data twice please some one help me
 

Nameless One

Senior Member
Mar 24, 2013
295
134
0
Tasmania
what i do with this ?
cm-12-20150320-INFECTED-yuga.zip.md5sum :confused:

and when i flash the rom via rcovery nothing happen just installing and never finish
i lose my data twice please some one help me
That file is used to check the integrity of the similarly named ROM file you have downloaded.
It contains a long hexadecimal number at the end of the first line of the file.

The downloader is expected to use a suitable app/program to create an md5sum for the downloaded copy they have of the ROM and compare the large hexadecimal number they get with the one for the original ROM copy on the author's computer (the one in the file you ask about for the ROM you have downloaded in this instance). If they are the same then the file downloaded is not corrupt.

suitable programs/apps:

http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html

for Windows

https://play.google.com/store/apps/details?id=com.o3tech.tools

for Android

OS X has a command line program called md5 which can be used via a terminal window.
 
  • Like
Reactions: omarsss98

stanstevo

Senior Member
Oct 27, 2013
65
19
0
I was wondering whether the dev can use ota update instead of creating a complete rom everyday, will be helpful to us reliant on mobile data.. Thanks for the superb work thou.
 

ChrisCh22

Senior Member
Dec 25, 2014
67
11
0
I was wondering whether the dev can use ota update instead of creating a complete rom everyday, will be helpful to us reliant on mobile data.. Thanks for the superb work thou.
The OTA updater in official CM12 (on other devices) downloads the entire 200+MB of the update, so there's no difference beside having to manually download and flash it. If you're referring to partial updates, such as those done with OpenDelta, then it needs to be implemented by the ROM developer, and I'm pretty sure it would require some sort of server modification. The point is, it's probably simpler for him to just create regular updates. If you're concerned about your bandwidth, update less often.
 

Nameless One

Senior Member
Mar 24, 2013
295
134
0
Tasmania
i try flash openrecovery-twrp-2.8.4.1-yuga by flashboot when i'm done my phone couldn't boot to rom, please help me
Did you do something like typing "fastboot flash boot <name of openrecovery file>" in Windows?

If you did then you have flashed a recovery image onto your phone's boot partition (the recovery image needs to be written to the FOTAKernel partition which if I remember correctly cannot be done with fastboot, it needs to be written to the FOTAkernel partition using either an Android app like Rashr or by using the dd command in a terminal window on the phone or via adb from the PC once the phone has booted to Android or by flashing within a suitable recovery).

To boot to Android you need to get a boot.img file from somewhere, the simplest way is to extract it from a ROM image .zip file, and then flash that in the same way you did the openrecovery image "fastboot flash boot boot.img".

If you have a copy of the openrecovery image saved on your phone then you can use the recovery you boot into now to flash a copy where it belongs on FOTAKernel first and then use fastboot to put a boot.img in the boot partition or use the recovery to dirty flash the current ROM over itself which should fix the boot partition.

Otherwise, if you don't have a copy of openrecovery saved on your phone, once you have fixed the boot partition as above and booted to Android on your phone you can then sort out the recovery.

twrp install instructions are here:

http://teamw.in/project/twrp2/187/
 
  • Like
Reactions: voduyxuyen

ibukamopa

New member
Dec 31, 2012
2
0
0
Most stable rom so far but...

Im currently using 2703 build and i can say that this is the most stable version so far. One thing i dont like is, 3g/H+ is not showing on the top of the navigation panel even i am connected to internet. I try to restart a couple of times but still no 3g icon shows.
 

AuSSiELaMbChOpS

Senior Member
May 27, 2012
433
1,270
0
github.com
Flashed the latest 5.0.2 build and it has been awesome just wondering if anybody can help with two questions I tried searching but didn't find anything helpful.

Is there an option to enable heads up notifications, I have searched through settings but can't for the life of me find it.

Had anybody got Smart Lock to work using a trusted location, it accepts the location but never keeps the phone unlocked and I keep having to enter my pin.

Sent from my Sony Xperia™ Z using Tapatalk
 

bradosav

New member
May 10, 2011
4
1
0
Some bugs

Thanks for the awesome ROM first off. I really like the clean interface and all the customizations CM has to offer.

I´ve been running the 20150327 version after flashing it over the 20150320. Sometimes the AudioFX keep crashing, as well as the SystemUI and SwiftKey Keyboard. This was happening even before the upgrade, but now the crashes are more frequent.

I´ve had another issue with this phone since I got it and tried different versions of the stock ROM, and some custom ROMs. The phone sometimes just will not wake up and I have to restart it. This is really frustrating as it tends to do that after I snooze my alarm, resulting in me waking up an hour late. Yesterday it just froze with the screen turned on. Is there a way to find out what is causing this? I suspect it is a hardware issue. Is there an app that would keep track of system errors and dump them to a time-stamped file? I´ve tried alogcat, but it only displays the log since boot. Would aLogrec do the trick? I´d really appreciate any insight!

Thanks!
 

AuSSiELaMbChOpS

Senior Member
May 27, 2012
433
1,270
0
github.com
Thanks for the awesome ROM first off. I really like the clean interface and all the customizations CM has to offer.

I´ve been running the 20150327 version after flashing it over the 20150320. Sometimes the AudioFX keep crashing, as well as the SystemUI and SwiftKey Keyboard. This was happening even before the upgrade, but now the crashes are more frequent.

I´ve had another issue with this phone since I got it and tried different versions of the stock ROM, and some custom ROMs. The phone sometimes just will not wake up and I have to restart it. This is really frustrating as it tends to do that after I snooze my alarm, resulting in me waking up an hour late. Yesterday it just froze with the screen turned on. Is there a way to find out what is causing this? I suspect it is a hardware issue. Is there an app that would keep track of system errors and dump them to a time-stamped file? I´ve tried alogcat, but it only displays the log since boot. Would aLogrec do the trick? I´d really appreciate any insight!

Thanks!
Have you tried a clean install to see if that fixes your problem? If you don't want to do a full factory reset you could try formatting the /system partition then reinstalling the rom, gapps & clear caches etc and see how that goes.

Logcat can provide details about apps that crash that might help track down the cause, also the file located at /proc/last_kmsg might provide insight into the sleep of death issues you are having.

Are you using any mods or things like Greenify that could be setup incorrectly and causing issues?
 

bradosav

New member
May 10, 2011
4
1
0
Weird things keep happening!

Have you tried a clean install to see if that fixes your problem? If you don't want to do a full factory reset you could try formatting the /system partition then reinstalling the rom, gapps & clear caches etc and see how that goes.

Logcat can provide details about apps that crash that might help track down the cause, also the file located at /proc/last_kmsg might provide insight into the sleep of death issues you are having.

Are you using any mods or things like Greenify that could be setup incorrectly and causing issues?
Thanks for the suggestions AuSSiELaMbChOpS, I´ve tried a clean install with other ROMs before, including the cm-12-2015320-INFECTED-yuga, and this kept happening. I will try the /proc/last_kmsg, too.

Yesterday I installed aLogrec, and let it record. I did not have any issues since! Perhaps it´s Murphy´s law, but maybe it has something to do with the log being continuously recorded. I will wait for a few days to see if the issue returns. If it does, I will try a clean install again and see. Thanks again!
 

bradosav

New member
May 10, 2011
4
1
0
Sleep of Death returns

Have you tried a clean install to see if that fixes your problem? If you don't want to do a full factory reset you could try formatting the /system partition then reinstalling the rom, gapps & clear caches etc and see how that goes.

Logcat can provide details about apps that crash that might help track down the cause, also the file located at /proc/last_kmsg might provide insight into the sleep of death issues you are having.

Are you using any mods or things like Greenify that could be setup incorrectly and causing issues?
Hi again, AuSSiELaMbChOpS,

I turned off alogrec and the sleep of death returned. I rebooted the phone and copied the /proc/last_kmsg and attached it to this post. I don't really know what to do with it. At the end it says no errors detected. I would really appreciate any help here. Thanks!
 

Attachments