• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM 10.2 Nightlies Discussion

Please guys... Don't thank me on my post. Thank TDM... All I did was sync his work and build it.

He's the one actually making things happen :)
 
This may just be me (something in my setup or whatever) but on the first official nightly, my lockscreen doesn't show up. The screen comes on, I can drag down the notification bar, sometimes I can swipe to unlock where the unlock icon should be and get the phone to unlock.... Pretty odd glitch.
 
Neph81 said:
I'm enjoying the nightly, but the damn camera/video glitch is happening. Time to start digging again.
Click to expand...

Yeah, this is really the only thing wrong. I could care less about the LG logo popping up sometimes.

Also, is there any difference between the bluetooth in Chameleon and this one? Because on this ROM I get a lot of audio dropouts while playing music through bluetooth (which unfortunately is the only way I can play music because I broke my headphone jack, oops). But I barely got them (audio drops) when I was on the Chaos ROM. It's not disconnecting completely, the audio just drops out almost like I'm getting a notification (but I'm not). I use Playerpro but I had the same issue on Apollo as well.
 
Nokoko said:
Clean flash, everything's working great so far! I had a lot of reboots on the last Beta, haven't had any so far on this, will update if I start having problems.
Click to expand...

Hi. I dirty flashed the current over CM 10.1, and things seem to be OK. So it's OK for me to clean flash this now? Which version did you flash, if I can ask? I want to make sure I get the correct version.

Of ALL the roms I've tried on this forum so far, this one seems to be the smoothest. I truly believe now what I've read here, that everyone's spectrum can/does act a little different from the others, and you have to try different roms to find the one that works best for you.

Well, I think I've found it. Thanks to everyone for this great rom.

P.S. NO LG Logo problems that I've seen.

UPDATE: OOPS, I did get a random LG logo using the phone app. Also, the shortcut for the phone app on the home screen says "app not installed". Have to delete it, and drag it from the app screen to get the phone shortcut to work. THEN, it automatically started a google setup for google "cards". Had to back out of it. Weird.
I wish this one would work perfectly, because this is the only rom so far that seems to give me really good battery life.
 
I get the same issue with the LG logo popping up intermittently. Usually seems to occur when making a theme, wallpaper, or system change. I am using Apex Launcher but it occurs with stock launcher as well. Also found I cannot use any other camera app. I have tried Camera Zoom FX and ProCapture. When opening either camera app the screen gets fuzzy static that locks up on the screen. The only way to get out of this is to hit the home button and then the app closes out. No errors. Tried rebooting the phone and clearing the cache on the phone apps. No luck. Using clean flash of ROM cm-10.2-20131018-NIGHTLY-vs920.zip. Please fix. No other issues yet. FYI. Found Camera360 Ultimate works on this ROM okay.
 
latest nightly (10/21) doesnthave working 4g at first boot. Maybe just my phone. 10/18 was fine. When i did clean install of 10/21, it got stuck on cyanogen mod boot animation, so had to pull battery. I was parandoid so i did another clean install, booted up successfully, but no mobile data even after waiting about 10 minutes. Rebooted into recovery to wipe data/ cache/ dalvik and 4g was working... i didnt want to do another clean install to save the time...
 
All you had to do was reboot after initial boot post-flashing, and cell signal and data will return. This is very common on Spectrum and CM based or AOSP based roms
 
TDM/Yoinx:
Update on camera issue. We're definitely looking at a buffer issue. I grabbed Focal from the market. The camera works, but has no video preview if you use the back camera. If you switch to the front camera, you have video preview, but are not able to take a photo. The constant Dmesg error is:
path_irq_0 - no free buffer

Following this error through a few threads I came upon this:
[KERNEL] MiRaGe - for HTC EVO3D Sense-ICS/AOSP-JB - 3.0.100 - 10132013 - Page 17 - xda-developers

Where they apparently fixed their issue by increasing the kernel SMI.
"I increased KERNEL SMI to 0x700000 and it seems not to crash anymore."

Does this info make sense to either of you? It's well above what I have time to look into as I'm in the middle of essay writing.
 
  • Like
Reactions: tdm
Heads up: cm merged some new telephony code today. Let me know how it affects the radios for tomorrow's build.
 
tdm said:
I'll need to figure out what SMI is. maybe rmcc has some more info.
Click to expand...



If I'm not mistaken that's just the amount of memory that you're allocating in the kernel. I had tried playing around with tweaking some of that stuff in the kernel builds I was doing for awhile. Which coincidentally, was when people started saying that some of the video stuff we had problems with before had started working running that kernel :dontknow:


I'm curious what their started at though.... because that only looks like they increased it to what... 7MB?


The values get defined under /lge/lge_board/i_vzw/board_i_vzw.c

These are the values from the CM10.2 Kernel tree. They start at line 1502, My browser is lagging too much to look at them too much though.

Code: 
#define MSM_PMEM_KERNEL_EBI1_SIZE  0x600000
#define MSM_PMEM_ADSP_SIZE         0x2000000
#define MSM_PMEM_AUDIO_SIZE        0x28B000
 
 
#define MSM_SMI_BASE          0x38000000
#define MSM_SMI_SIZE          0x4000000
 
 
#define KERNEL_SMI_BASE       (MSM_SMI_BASE)
#define KERNEL_SMI_SIZE       0x600000
 
 
#define USER_SMI_BASE         (KERNEL_SMI_BASE + KERNEL_SMI_SIZE)
#define USER_SMI_SIZE         (MSM_SMI_SIZE - KERNEL_SMI_SIZE)
#define MSM_PMEM_SMIPOOL_SIZE USER_SMI_SIZE
 
 
#define MSM_ION_SF_SIZE                0x4000000 /* 64MB */
#define MSM_ION_CAMERA_SIZE     MSM_PMEM_ADSP_SIZE
#define MSM_ION_MM_FW_SIZE        0x200000 /* (2MB) */
#define MSM_ION_MM_SIZE                0x3600000 /* (54MB) */
#define MSM_ION_MFC_SIZE        SZ_8K
#ifdef IPRJ_ION_MEM_SETTING
#define MSM_ION_WB_SIZE                0x2100000 /* 33MB */
#else
#define MSM_ION_WB_SIZE                0x610000 /* 6MB */
#endif
#define MSM_ION_QSECOM_SIZE        0x600000 /* (6MB) */
#define MSM_ION_AUDIO_SIZE        MSM_PMEM_AUDIO_SIZE
 
 
#ifdef CONFIG_MSM_MULTIMEDIA_USE_ION
#define MSM_ION_HEAP_NUM        9
#define MSM_HDMI_PRIM_ION_SF_SIZE MSM_HDMI_PRIM_PMEM_SF_SIZE


Not too sure if you can actually kick those up too much. But the kernel is currently being allocated pmem_adsp_size which should be about 32MB. It seems like 32MB of buffer *should* be plenty, you could try doubling that.... but I'm pretty sure that you would need to balance something else in the memory allocation somwhere.

I've felt like this rom shows more ram available to the user than what CM10.1 did. Being that that's essentially the PMEM/User split... I was kinda wonder what we regained from PMEM to always have more available ;) The values don't look different from the CM10.1 kernel, but maybe something in the memory management code is making more available that it really shouldn't be.
 
  • Like
Reactions: tdm
It very well could be that some value changed that should not have or it could be the memory issue is just the symptom of something bigger that I'll need to dig into. I'll keep digging, but at least now I have a camera app that doesn't crash while still providing me error info that I can dig into.
 
I tried a clean install of build cm-10.2-20131021-NIGHTLY-vs920.zip last night but still having camera issues. Also getting error on Alarm Clock Pro by iHandySoft Inc."Unfortunately, Alarm Clock has stopped." Updated to cm-10.2-20131022-NIGHTLY-vs920.zip. Alarm Clock Pro got error on first launch then worked fine after subsequent launches. Other camera apps still having the same issue.

FYI.
The camera issue does not occur on the cm-10.1.3-vs920.zip or the cm-10.1-20131007-NIGHTLY-vs920.zip ROM builds.

Found this in the change log for the cm-10.1-20131007-NIGHTLY-vs920.zip ROM build.

http://review.cyanogenmod.org/#/c/50240/

Hope this helps.
 
10/22 build works fine except I did have to reboot to get data back. Camera and video works fine for me on this build. This build is my daily driver and I'm a GI physician on call tonight and no messaging/phone call/internet issues.
 
  • Like
Reactions: tdm
HueyT said:
10/22 build works fine except I did have to reboot to get data back. Camera and video works fine for me on this build. This build is my daily driver and I'm a GI physician on call tonight and no messaging/phone call/internet issues.
Click to expand...

Thanks. I want to build data on how this new qcril acts for CDMA and LTE.

Here is a rundown of the various ROM reactions to it:

CM is obviously going for it.

PAC, being mainly CM based, will implement it.

AOKP has also decided to implement it, as they have always relied on CM for hardware and telephony support.

Omni, being divorced from CM by virtue of my PACE work, is completely unaffected and I haven't heard any mention of implementing it.

Gummy has forked all hardware and telephony repos from CM and is now basically in the same boat as omni.

I will keep PACE on the current code.

PA are nexus snobs and still uses aosp telephony.
 
I'm, in theory, getting better signal on the 102213 nightly. I won't know for sure until I go to work tomorrow, where getting signal tends to be harder. The camera still has the same issues as before.
 
You must log in or register to reply here.
Back
Top Bottom