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

Root [ROM] Quattrimus JB (CM10, AOKP41)

jfatica said:
On the topic of reboots..

I've had 5 spectrums since April, and they've all had random reboots.. some more frequently than others. My latest one has been stable for about 3 weeks. I was only able to pinpoint and repeat one of the issues I had with a past phone, it was the car sensor randomly triggering and loading the car dock app...then causing a reboot.

This has happened on stock GB, Black Plague, Broken Out, and stock ICS. So far no problems on CM10. Although now that I'm hearing reports of reboots I'm a little nervous.

I think this is just a cheaply made phone.
Click to expand...

Funny thing is I'm on my first spectrum that I've had since March and never had a terrible time with reboots on any of the roms but I've had a lot on Cm10. But pretty much all have been while playing bridge construction kit.

This phone is an enigma
 
IMUcarmen said:
Funny thing is I'm on my first spectrum that I've had since March and never had a terrible time with reboots on any of the roms but I've had a lot on Cm10. But pretty much all have been while playing bridge construction kit.

This phone is an enigma
Click to expand...
LG's quality control standards have always been seriously lacking.
 
MrB206 said:
Yea, but I changed the dpi before and didn't see that error. Lemme set it back to 320 and see what happens.
*edit* no dice to both.
Click to expand...

Have that problem on my tablet, have to change the DPI back to default, clear cache for Play Store and Google Play Services and reboot.
 
MrB206 said:
Just came across this after I wiped data and flashed beta 4. Anyone else see this error?
Click to expand...

I had originally flashed an inverted version of Gapps on my phone and it caused search to not work while every other google app did work. I flashed the gapps version from the OP over it and restarted my phone. Play store notified me that there was an update available, it updated and haven't had a problem since. I also have my DPI set at lower than stock.

tldr; reflash gapps from OP
 
tdm,

This is the only code I could find in there that seemed to relate to the problem. Can you make any sense of it?

Code: 
/* Apply any per-cpu voltage decreases. */
static void decrease_vdd(int cpu, unsigned int vdd_sc, unsigned int vdd_mem,
			 unsigned int vdd_dig, enum setrate_reason reason)
{
	int ret;

There is also some code that I don't quite understand a ways down from this that looks like it could be there.
 
IMUcarmen said:
yea I've been getting that too. With google search, and a few other apps as well.
Click to expand...

Mystery solved. Play Store had to update to the newest version and then Google Search was available for update. It's a shame we can't force the update of the Google apps like Play Store.
 
MrB206 said:
Mystery solved. Play Store had to update to the newest version and then Google Search was available for update. It's a shame we can't force the update of the Google apps like Play Store.
Click to expand...

the new play store sucks. I hate it so much now.
 
ortrigger said:
tdm,

This is the only code I could find in there that seemed to relate to the problem. Can you make any sense of it?

Code: 
/* Apply any per-cpu voltage decreases. */
static void decrease_vdd(int cpu, unsigned int vdd_sc, unsigned int vdd_mem,
 unsigned int vdd_dig, enum setrate_reason reason)
{
int ret;

There is also some code that I don't quite understand a ways down from this that looks like it could be there.
Click to expand...

Thanks. I'll need to study the code. Probably later today or tomorrow.
 
MrB206 said:
Mystery solved. Play Store had to update to the newest version and then Google Search was available for update. It's a shame we can't force the update of the Google apps like Play Store.
Click to expand...

Is there a way to make the play store check for updates?
 
tdm said:
Where would I find an example of this in a ROM?
Click to expand...

If we are talking about what I think we are talking about, it is a stock LG settings function. You should be able to find it in any official spectrum release, I looked for an apk, but I don't see anything that rings a bell.

When you went to system settings there was a sub menu to change/fix app display size or something. I never tried it as I never had a need for it.
 
tdm said:
Thanks. I'll need to study the code. Probably later today or tomorrow.
Click to expand...

The other code I was talking about is another 100 lines or so down. Good luck with it. If I was more advanced in my coding abilities I could probably help more but for now that's what I've got.
 
  • Like
Reactions: tdm
finndo77 said:
If we are talking about what I think we are talking about, it is a stock LG settings function. You should be able to find it in any official spectrum release, I looked for an apk, but I don't see anything that rings a bell.

When you went to system settings there was a sub menu to change/fix app display size or something. I never tried it as I never had a need for it.
Click to expand...

I'd it can only be found in the vendor proprietary ROM, then no, I almost surely can't get it to work.
 
Looking at that voltage regulator code closer, it seems the infraction is one core trying to set the voltage for the other core. Apparently a core can only set its own voltage. That makes some sense, as the regulators may be on-core (don't know, just a guess).

I should have more information on this in a few days, as I collect stack dumps and do a bit more investigation.

I'll try to post an instrumented kernel and a script to save off last_kmsg on boot later today. The more phones that collect info, the faster it can be diagnosed and fixed.

Remember, any time a phone reboots unexpectedly, that is a bug. Be sure to post /proc/last_kmsg on pastebin and post a link to let me know.
 
tdm said:
Looking at that voltage regulator code closer, it seems the infraction is one core trying to set the voltage for the other core. Apparently a core can only set its own voltage. That makes some sense, as the regulators may be on-core (don't know, just a guess).

I should have more information on this in a few days, as I collect stack dumps and do a bit more investigation.

I'll try to post an instrumented kernel and a script to save off last_kmsg on boot later today. The more phones that collect info, the faster it can be diagnosed and fixed.

Remember, any time a phone reboots unexpectedly, that is a bug. Be sure to post /proc/last_kmsg on pastebin and post a link to let me know.
Click to expand...

Thanks for your dedication to this. I'll be sure to grab last_kmesg if I have any random reboots on my spec. If you need anything else, let me know.
 
  • Like
Reactions: tdm
Never lose a last_kmsg again! Here's a simple little script to save and rotate the last ten last_kmsg files in /data/local/tmp. Copy it to /system/etc/init.d directory, name it something like 02kmsg, and make it executable (mode 555). I might include this in my next build.

Code: 
#!/system/bin/sh

logdir=/data/local/tmp

mkdir -p $logdir

basefile=$logdir/last_kmsg

if [ -f /proc/last_kmsg ]; then
	if [ -e $basefile.9 ]; then
		rm $basefile.9
	fi
	for n in 8 7 6 5 4 3 2 1 0; do
		if [ -e $basefile.$n ]; then
			mv $basefile.$n $basefile.$(($n+1))
		fi
	done
	cp /proc/last_kmsg $basefile.0
fi
 
tdm said:
Okay .. OP updated with beta4. Looks like there are 8 bugs and 2 requests in the tracker right now. Here's my take on priorities:

High priority:

* Camera + power reboot.
* GPS functionality.

Medium priority:

* Power off charging.
* Baseband version string.
* Bluetooth MAC.

Low priority:

* WiFi Direct.
* 1080p video decoding.
* Apollo crash with adblocker.
Click to expand...

Thanks for this tdm! Maybe a suggestion - GPS could be medium priority. I don't know which post I read, but I downloaded GPS Status from Play Store and it got my GPS to work. The first few times it did take a while, but it does work for me at least.
 
@tdm: I'm using your init.d script from above to try and catch my gps reboot issue off rooted stock rom. In the ksmg file that is output it has two lines that seem relevant:

[ 0.973693] CRASH LOG START ADDR : 0x77340000
[ 0.973785] CRASH LOG END ADDR : 0x77340fff

http://pastebin.com/P1HD24Bj

any idea what I could do next?
 
  • Like
Reactions: tdm
androidslam said:
@tdm: I'm using your init.d script from above to try and catch my gps reboot issue off rooted stock rom. In the ksmg file that is output it has two lines that seem relevant:

[ 0.973693] CRASH LOG START ADDR : 0x77340000
[ 0.973785] CRASH LOG END ADDR : 0x77340fff

[ 0.000000] Booting Linux on physical CPU 0 [ 0.000000] Initializing cgro - Pastebin.com

any idea what I could do next?
Click to expand...

Glad to see the script is bringing in logs. :)

The CRASH LOG entries at startup are just informational to show the physical address of the log buffer. They are normal and present with every boot.

Any entries related to a crash will be near the end of the log, within a couple seconds of the last entry. In your case:

[ 782.420684] QSEECOM: qseecom_release: data->released == false
[ 783.031402] SysRq : Emergency Remount R/O

The QSEECOM message seems to be normal and benign.

If the Emergency Remount message is present, there is usually nothing relevant after it.

Which is to say, there is basically nothing useful in that log. And that is BS. I need to add a stack dump to the Emergency Remount message to find out what is causing this.
 
Haha. Ok. Thanks again for taking a look at the log and putting together the script that produced too. :) For me, anything helps in trying to understand this stuff. I'm trying to diagnose the gps reboot issue on stock because I started experiencing the same reboot issues on cm10 once you added the gps files into the builds.

For anyone else who is interested I followed this link to set up the init.d on my rooted stock ICS spectrum:

http://forum.xda-developers.com/showthread.php?t=1933849

From there I just set it up like tdm stated in post #816.
 
yo, I need a bit of help...I flashed cm10 over to my spectrum, the messaging kept crashing so I restarted my phone and it put my phone in a bootloop. Now I can only flash gb based roms on my spectrum or I get bootlooped
 
You must log in or register to reply here.
Back
Top Bottom