[ROM] VCRom v007
- Thread starter zefie
- Start date
Manual
If you are asking me, yes. I used the LG tool. But now that I have VCRom 005, it is asking to update, on it's own. I would assume, it is because the kernel is different. I don't know myself, just a guess.
If you are asking me, yes. I used the LG tool. But now that I have VCRom 005, it is asking to update, on it's own. I would assume, it is because the kernel is different. I don't know myself, just a guess.
Last edited:
Better LogCat
Try this one instead, check out PID/thread 2034
A little more than halfway down:
D/vending ( 2034): [10] DeviceConfigurationReceiver$1.run(): Clearing cache in response to android.intent.action.SIM_STATE_CHANGED
Try this one instead, check out PID/thread 2034
A little more than halfway down:
D/vending ( 2034): [10] DeviceConfigurationReceiver$1.run(): Clearing cache in response to android.intent.action.SIM_STATE_CHANGED
Wow zefie... I didn't even realize you have made multiple releases in such a short fashion... I am still running v3 with my Gingerbread theme (since it is black)... 
Some comments/questions:
1) Could we use custom build props from Thunder for this? I see wifi.supplicant_scan_interval is still set to 20. The new props have this set to 60 to save power. If we cannot use old props from ThundeROM, consider implementing this change?
2) Could you move the Sprint Zone apk out of system? Easier to remove that way.
3) Does the battery icon show percentage remaining like on many of the customized themes? Just curious
4) Does updating from v3 require a wipe on anything? Or does your update script handle this? Like the removal of IQAgent, etc... Thanks.
Some comments/questions:
1) Could we use custom build props from Thunder for this? I see wifi.supplicant_scan_interval is still set to 20. The new props have this set to 60 to save power. If we cannot use old props from ThundeROM, consider implementing this change?
2) Could you move the Sprint Zone apk out of system? Easier to remove that way.
3) Does the battery icon show percentage remaining like on many of the customized themes? Just curious
4) Does updating from v3 require a wipe on anything? Or does your update script handle this? Like the removal of IQAgent, etc... Thanks.
Wow zefie... I didn't even realize you have made multiple releases in such a short fashion... I am still running v3 with my Gingerbread theme (since it is black)...
Some comments/questions:
1) Could we use custom build props from Thunder for this? I see wifi.supplicant_scan_interval is still set to 20. The new props have this set to 60 to save power. If we cannot use old props from ThundeROM, consider implementing this change?
2) Could you move the Sprint Zone apk out of system? Easier to remove that way.
3) Does the battery icon show percentage remaining like on many of the customized themes? Just curious
4) Does updating from v3 require a wipe on anything? Or does your update script handle this? Like the removal of IQAgent, etc... Thanks.
1) In testing for 007, but I'm gonna slow my releases. Another build prop should work but may trigger OTA update to harass you, not sure what triggers that yet. I'd suggest manually pulling and editing the file from 006 for now.
2) I like to keep as many distributed apk's on system as possible to retain more room for /data. Here is a quick set of commands to remove SprintZone:
adb reboot recovery
adb shell mount /system
adb shell rm /system/app/SprintZone.apk
adb shell reboot
3) The battery icon shows 1-100 in all intervals but only shows the number when unplugged. It does not do the blinky thing most others do because that annoys the crap out of me lol.
4) Update should handle everything. Wipe /data if it fails to boot but you shouldn't need to.
Thanks for the reply.
As far as an OTA nag, I haven't gotten any yet on any of the configurations I have been on... Maybe I am excluded from OTA...
As far as an OTA nag, I haven't gotten any yet on any of the configurations I have been on... Maybe I am excluded from OTA...
006?
@zefie
If your testing for 007, do you have 006 to release, with the possible fix to the nag. Anything is worth a shot.
@zefie
If your testing for 007, do you have 006 to release, with the possible fix to the nag. Anything is worth a shot.
Since I goofed on something and have to repackage 006 I'm going to put that wifi tweak in 006. So it will be another hour or so before 006 is ready.
Still there
The OTA harassment is still there, but love the Nexus boot animation. Here is a LC, in case you want it for troubleshooting the OTA.
EDIT - This was flashed on top of 005.
The OTA harassment is still there, but love the Nexus boot animation. Here is a LC, in case you want it for troubleshooting the OTA.
EDIT - This was flashed on top of 005.
Try wiping /data I don't really see what could be triggering it when I updated the strings. gonna have to wait until i get offered it i guess.
Do you think you could tie in a reboot, and a reboot into recovery option like LEGO did? In a future build...
Reboot
I have that, just putting in a request. But it's your ROM, and a nice one at that. Thanks again.
I have that, just putting in a request. But it's your ROM, and a nice one at that. Thanks again.
Similar threads
Trending Posts
-
-
-
Question Bluetooth keeps on turning off automatically at 10 minutes interval
- Started by Ayatokirizka
- Replies: 5
-
otb 20+ 5G VERIZON stuck on 10
- Started by watertraveler
- Replies: 3
-
Facebook
Twitter
Instagram