• 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

OK, here is where we're at. The databases populate exactly the same, except for one column. The "current" column has no info on the bad database, but certain ones are filled in with a 1 on the good database. My guess is that this info is needed to choose the current APN to run. TDM, I'm sending you both DB files as well as the converted .xls files.
 
I think I found the problem -- for some reason the radio layer doesn't "see" the last response from the RIL when it's requesting RUIM records. This can be seen by comparing good vs. bad radio logs and searching for "RuimRecords".

I've reached out to rmcc, who put me in touch with a CDMA guy. Hope to have a fix soon.
 
Also, getting my AOSP ROM polished up. Should have something functional soon. Watch here:

https://github.com/pace-rom

This currently contains all the CAF and CM picks necessary to boot and run on Find5 and P930. VS920 compiles but the default compiler doesn't seem to spit out a functional kernel for some reason.

I just forked the kernels, but don't have the device or vendor trees up yet.

Currently working: WiFi, cameras.
Currently broken: radio, Bluetooth.
 
Are the issues with camera/photo apps due to dirty flashing? I can't post pictures to instagram (when you hit the picture button you get the static screen and when you try to use the share button it won't let you get past the filter part). The only apps that use a camera I can get to work are the actual camera app (but not for videos) and snapchat.

Also I'm having a lot of issues with random reboots and freezes.
 
oceania said:
Are the issues with camera/photo apps due to dirty flashing? I can't post pictures to instagram (when you hit the picture button you get the static screen and when you try to use the share button it won't let you get past the filter part). The only apps that use a camera I can get to work are the actual camera app (but not for videos) and snapchat.

Also I'm having a lot of issues with random reboots and freezes.
Click to expand...
On a clean flash with the fixed telephony.db I still have camera issues, so I'm going to say that this is ROM related at the moment. As far as reboots and freezes, anything I've encounted has been app related. Case in point, Noom, which includes a pedometer, will cause issues with my phone. Once I uninstall it or pause the pedometer function, the issues go away. I'd say this ROM is rock solid otherwise.
 
I am still on Test build 20130904 and I dirty flashed+gapps for 4.3 and phone works good until today phone started a random reboot. I replaced another battery - still happening. I uninstalled Maps, Facebook, Chrome then reinstalled it again. The phone works good all day. I see that apps in old android version need to reinstall again. Strongly recommend to uninstall all apps before dirty flashing the cm 10.2.
Another issue I know about it - the unmount SD card. It does not work properly. I hate to see "Scanning SD card for errors", also all video records and pictures gone in the library, but in my computer I see all fine with usb card reader.
 
I've been unable to catch a logcat of it, since I've been really busy and it only happens when I'm not around a computer.

Occasionally when an app redraws, the system will draw the LG logo (similar to boot up) then redraw the app screen correctly. It only does this for the app area, the status bar stays visible and correctly drawn.

Kinda weird.

Btw, it does this on both the CM10.2 beta2 as well your PACE rom. I'd assume it's kernel related. Don't see a point reporting it on both threads though.
 
  • Like
Reactions: tdm
Also, is this missing the cm privacy guard stuff because it's an unofficial beta or is that gone in. 10.2?

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Also, is this missing the cm privacy guard stuff because it's an unofficial beta or is that gone in. 10.2?

Sent from my VS920 4G using Tapatalk 2
Click to expand...

That's actually a feature that was quietly slipped into Android 4.3. I know that Trickster Mod can pull up the menu for you. There may be others as well.
 
I saw someone mention about auto brightness not working as well as the phone screen not reliably turning back on after pulling the phone away from their head. Though I can't remember which thread this info was in (this one or pace)

I can confirm that the light sensor is not working as intended. Using elixir 2 to read the data off the sensors, neither the light sensor or proximity sensor is actually outputting any data. This can be seen under sensors then tapping the play icon on the sensor.

The sensor vendor and such is reporting correctly... just no data is being generated.

*edit*
It does work... but it doesn't report right. I get 3 lux in low light, 12 in room light and 10000 lux with a flashlight pressed against the sensor. The auto brightness settings just need to edited to reflect this I guess. Can be done user side.... just seems like it's reporting values at 1/10th of what they should be.

ortrigger said:
That's actually a feature that was quietly slipped into Android 4.3. I know that Trickster Mod can pull up the menu for you. There may be others as well.
Click to expand...

Thanks it's called app opps now, it's one of the hidden device menus but I don't know the code to access it. Trickster did the job though.

Sent from my VS920 4G using Tapatalk 2
 
tdm said:
Noticed there have been some telephony changes lately so I made a new build. Please let me know if data works after a clean flash.
Click to expand...
Up and running after full wipe and clean install. No mobile data on first boot, but clean 4g on second and subsequent boots.
 
TDM, it seems Test build 20131003 refuses to install in TWRP 2.6.0.0 with the error "set_perm: some changes failed" while Test build 20130918 installed, but LTE won't work, it shows a signal but mobile state shows up as disconnected no matter what it seems.
 
scibot said:
TDM, it seems Test build 20131003 refuses to install in TWRP 2.6.0.0 with the error "set_perm: some changes failed" while Test build 20130918 installed, but LTE won't work, it shows a signal but mobile state shows up as disconnected no matter what it seems.
Click to expand...

Get a copy of the recovery log.
 
I also use TWRP 2.6.0.0 and there is no problem with the zip. Recheck download and MD5. Make sure you clean wipe system, data, dalvik cache, regular cache, android-secure before flashing. Initial boot may show no data but reboot will bring 3G/4G back.
 
FYI, I have 4G on the first boot. It took a while for it to show up, but I did not require a reboot. I'd like to think this issue is now fixed. I believe that just leaves the camera API and we should be ready to submit for official nightlies again.
 
HueyT said:
I also use TWRP 2.6.0.0 and there is no problem with the zip. Recheck download and MD5. Make sure you clean wipe system, data, dalvik cache, regular cache, android-secure before flashing. Initial boot may show no data but reboot will bring 3G/4G back.
Click to expand...

Alright Thanks, I re-downloaded the rom and it installed the first time! Not sure what happened but that is now fixed and I can confirm 4G works after a reboot as well.
 
Neph81 said:
FYI, I have 4G on the first boot. It took a while for it to show up, but I did not require a reboot. I'd like to think this issue is now fixed. I believe that just leaves the camera API and we should be ready to submit for official nightlies again.
Click to expand...

Camera API? What is wrong with that?
 
Neph81 said:
FYI, I have 4G on the first boot. It took a while for it to show up, but I did not require a reboot. I'd like to think this issue is now fixed. I believe that just leaves the camera API and we should be ready to submit for official nightlies again.
Click to expand...
Confirmed: mobile data 4g on first boot after full wipe and clean install. took ~3 full minutes to boot/initialize for me, but working great after that.
 
Neph81 said:
FYI, I have 4G on the first boot. It took a while for it to show up, but I did not require a reboot. I'd like to think this issue is now fixed. I believe that just leaves the camera API and we should be ready to submit for official nightlies again.
Click to expand...

As I posted a few posts back, the light sensor doesn't seem to be reporting light changes too well... unless that's just my phone.

Sent from my VS920 4G using Tapatalk 2
 
You must log in or register to reply here.
Back
Top Bottom