yashsingh1/xdaforums huggingface dataset:
[LG Nitro HD] jurassic512:
Sweet ROM so far except for my Wi-Fi. Is anyone else having problems connecting and staying connected with WiFi? I came from CM10 and my WiFi connection was fine. I was able to download an app from the Play Store, but it was horribly slow, and sometimes with WiFi enabled, i won't even get the signal bars. Also at times after finding my modem, it will switch to out of range when it's 3ft from the modem.

I've power cycled and reset my modem via Setup

Rebooted my phone a couple times

Triple checked any settings I may have made affecting WiFi

Okay this is weird. I changed the Network Name on my modem thinking it would help me get a stable connection, and it showed in the WiFi settings on my phone, but when i disable and re-enable WiFi on my phone, , the old and new Network Name are there and the new one is Out of Range. It will allow me to forget the old name, but the only option for the new name is Connect or Cancel.

Getting weirder now. I did a factory reset, wipe, dalvik, then attempted to reflash your ROM, and it says:

...

symlink: some symlinks failed

E: Error in /sdcard/quattrimus-iproj-aokp41-beta4.zip

(status 7)

Installation Aborted :(
[LG Nitro HD] tdm:
Can you get me a complete log of the install? It should be in /tmp/recovery.log or something similar. Just grab it with adb and post it on pastebin.

Thx!
[LG Nitro HD] tdm:
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.
[LG Nitro HD] jurassic512:
I did a search on my phone for *.log after I couldn't find that path you suggested, and all i have is sdcard/fix_permissions.log

Update:

Well I was able to flash CM10 back, so I tried your ROM again and it installed without error, but WiFi is still not working. So I go back to CM10, and guess what? My WiFi is acting the same way as it did on your ROM.

Signed,

Sad Sad Panda.
[LG Nitro HD] tdm:
The recovery.log will be in /tmp while you are in recovery. When you reboot, the recovery copies that file over to somewhere in /cache. Maybe /cache/recovery_log or something. Search and you'll find it.

Get a logcat of the failed wifi connection and post it on pastebin, I'll take a look to see if anything stands out.
[LG Nitro HD] 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.

#!/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
[LG Nitro HD] jurassic512:
I did not see recovery.log in recovery. Maybe I deleted it when i restored my CM10 backup.
[LG Nitro HD] Maverick.Marq:
Random reboot

http://pastebin.com/xMzREew2
[LG Nitro HD] tdm:
Another mysterious sysrq invocation. I'll have a new build tomorrow to debug that.
[LG Nitro HD] lionman229:
being by far the most active thread ill just post this here. the CM10 just merged a new kernel i think. Refer to the BBQLOG

http://changelog.bbqdroid.org/#p930/cm10/1357139922
[LG Nitro HD] tdm:
Don't know why that shows up but it isn't the iproj kernel.
[LG Nitro HD] lionman229:
Worst news ever
[LG Nitro HD] khanfed:
Does anyone else notice that contact (phoonebook ) search is case sensitive now?

Not sure if it was always like that.
[LG Nitro HD] tdm:
Got aosp41 booted and running. Brief overview:

Working:

* WiFi

* Bluetooth

* Back camera

Not working:

* Firmware links are not being created at first boot.

* Default RIL is not working, need CM's LGEQualcommUiccRIL and related stuff.

* Front camera

* USB storage
[LG Nitro HD] Maverick.Marq:
I vote yes to this
[LG Nitro HD] tdm:
Busted! Adding the Qualcomm RIL stuff breaks the build...

target Dex: framework

trouble writing output: Too many methods: 65540; max is 65536. By package:

And this, ladies and gents, is why CM has framework2.jar. Need to get that going next.
[LG Nitro HD] Maverick.Marq:
Is this a phone limitation or android?

Does this also affect aokp?
[LG Nitro HD] tdm:
It's android, actually dalvik. CM and AOKP both have worked around it. And I need to also apparently.
[LG Nitro HD] tdm:
aokp42 anyone...? :)

http://rootzwiki.com/news/_/articles/first-official-aokp-42-build-released-r1313
[LG Nitro HD] lordcheeto03:
Some 4.2 love would be sweet!
[LG Nitro HD] altvolt74:
TDMCODE WOULD. U PORT IT.. if is so AWESOME! !!! MAKE MY DREAMS COME TRUE!!!!! PLZ LOL:p
[LG Nitro HD] lordcheeto03:
Just be patient. I would imagine he's working on it.
[LG Nitro HD] tdm:
Absolutely not. I do not do ports.

But I will try to compile it. :)
[LG Nitro HD] tdm:
I got the framework issue sorted out and now I'm debugging the RIL.

But I found something interesting...

I installed aosp41 and poked around a bit, then went to restore my backup of aokp41. But I accidentally hit backup instead of restore. And I noticed that the directory was named with the correct date/time. Previously, on both my nitro and spectrum, the date was wacky (1970 I think). I wonder what happened to fix that...?
[LG Nitro HD] tdm:
For those wanting AOSP and brave enough to be a guinea pig...

quattrimus-iproj-aosp41-test.zip

Known issues:

* Front camera doesn't work. If you select it, wipe gallery data to get the camera app back.
[LG Nitro HD] tdm:
FYI, I posted beta5 on getquattrimus.com. I don't have time to do a full mirror and update yet, hopefully by Monday. But if you're looking for a new ROM to flash, give it a try.

Changes off the top of my head:

* Hopefully fixed bluetooth crash.

* More kernel debugging.

* kmsg script.

* SU640 support added. SU640 users please give feedback!
[LG Nitro HD] tdm:
Spectrum users report that 4G may not be stable. I don't have 4G with StraightTalk so please let me know how 4G works compared to CM10/AOKP41. Thx!
[LG Nitro HD] jurassic512:
All I see are beta 2's.
[LG Nitro HD] tdm:
Go for the deep link...

http://getquattrimus.com/roms/quattrimus/iproj/quattrimus-iproj-cm10-beta5.zip
[LG Nitro HD] tdm:
OP updated with beta5 links.
[LG Nitro HD] drumist:
What I've observed is that if you "cold boot" to recovery (volume down + power button), backups you make will show as ~1970. But if you "warm boot" to recovery (for example, "reboot to recovery" from power menu) the date/time will be correct.

Assuming you're familiar with the difference between the real-time clock and "system" clock, you can probably figure out why this happens. Basically the real-time clock is never being updated and has been counting from 0 (unix epoch) since manufacture.
[LG Nitro HD] jeonaztigz:
does this remove the 80 sms char limit on SU640? Is there a method to remove that limit? I use go sms but the msg cut out on 80. Stressed
[LG Nitro HD] Maverick.Marq:
WiFi toggle was giving me some trouble but eventually worked had to turn it on and off a couple times. Can't install apps that store info on SD card durring install (xda-developers app) but I can access the SD card fine with es file explorer app
[LG Nitro HD] tdm:
I don't know. Try it and see. If it's a Rom limitation, then probably yes. If it's a carrier limitation, then no.

I don't have a su640, I just used the CM10 kernel config and added detection for the device in the installer.

Please let me know if the install script detects the i_skt model. Also let me know how everything works.

Thx!
[LG Nitro HD] xordos:
Yes, I also feel other recording app is using noise cancelling mic too, for example: Tape-a-Talk (and wechat etc.)

I am using AOKP beta5 20130102.
[LG Nitro HD] aquariuz23:
Tdmcode, I'm a little confused with beta5, n I apologize if u did mention somewhere here wat it actually is, but is beta5 = jb 4.2 ?
[LG Nitro HD] tdm:
No still 4.1
[LG Nitro HD] jeonaztigz:
Just w8 for my feedback sir, i try the AOSP
[LG Nitro HD] tdm:
AOSP does not have SU640 support yet.

Beta5 for both CM10 and AOKP41 do have SU640 support.

An LU6200 user finally contacted me, so I expect beta6 will have LU6200 support also. :)
[LG Nitro HD] tdm:
Sent an email to the codeaurora developer who introduced the code which is causing the cpufreq crash. Hopefully he will respond.

I know enough about the code to see what's happening. In a nutshell, cpu#0 is running and cpu#1 is offline/disabled. This is normal. Something decides to bring cpu#1 online (presumably due to need for increased processing power). The hardware code that sets the cpu parameters is supposed to be run on the same cpu that it's setting (that is, cpu#1). Usually this is the case, but sometimes cpu#0 is running the code. This is apparently invalid and causes the code to fail, which in turn causes the kernel to crash and reboot.

Unfortunately, I don't know enough about the code or the hardware to come up with a good solution yet.

So far my best solution is to just remove that check. But I don't know what will happen if cpu#0 tries to set the parameters for cpu#1. It may work okay or it may cause an invalid hardware state and reboot anyway.

All other solutions would require deeper investigation into the kernel scheduler. For example, detecting the situation and (re)scheduling cpu#1 to run the code. Or perhaps making the notifier call chain atomic so that the scheduler can't switch out the running cpu from underneath us.
[LG Nitro HD] tdm:
No response from the codeaurora developer yet, but I went ahead and looked at it anyway.

tl;dr: I think I've got a fix coded.

Long story:

It appears the vendor binary /system/bin/mpdecision is responsible for deciding when to enable/disable te second core (so mpdecision is surely short for Multi Processor Decision), based on finding these strings in the binary:

/sys/devices/system/cpu/cpu%d/online

/sys/devices/system/cpu/cpu0/rq-stats/run_queue_avg

It would seem that it monitors the cpu load and turns cpu1 on/off when needed. Interesting find, but not terribly relevant.

So the problem is that cpu0 is running code to set voltage for cpu1, but only when userspace sets cpu1 online (via that sys file above). I found some kernel apis that allow me to invoke a function on a different cpu, which is exactly what we need in this case: if we find we're trying to set the voltage from the wrong cpu, invoke it on the right one instead.

I was in the middle of coding up a solution when my wife called me and the phone rebooted with the same exact issue I was trying to fix. :mad: Apropos but not terribly relevant.

Anyway, so I got the fix all coded up and it seems to work. So I'll be pushing out a test ROM later today to see if that fixes the issue.
[LG Nitro HD] lordcheeto03:
Wish I knew enough to fully, or at least half-way understand what's going on instead of just the general idea. :\ But regardless, thank you for the hard work you put into being an active contributor to this device!
[LG Nitro HD] Maverick.Marq:
Just got my nexus 4 but I'll still be flashing these Roms and testing them regularly
[LG Nitro HD] tdm:
Had some other things to do this afternoon, I probably won't be able to get a new ROM with the cpufreq crash fix out until tomorrow. I'll also look at the voicemail thing. And beta6 will have LU6200 support also.
[LG Nitro HD] tdm:
Nevermind about the voicemail thing, that's for the VS920.... too much copy/paste today. ;)
[LG Nitro HD] tdm:
beta6 is up, check the OP.

Changes:

* Fixed cpufreq crash.

* Fixed bluetooth mac.

* Added voicemail setting for i_vzw.

* Added experimental i_lgu (LU6200) support.
[LG Nitro HD] Flyview:
Hey guys,

I figured I would update to the latest CWM and did it through ROM Manager. It updated from 5.8.2.0 (which was working well) to 6.0.1.5. It does not work well. A backup took >30minutes and had an error close to the end. Where do I get 6.0.1.1?
[LG Nitro HD] tdm:
I'm using CWMT 6.0.1.5. Works great. Link.
[LG Nitro HD] Flyview:
Hmmm thanks. Weird I just checked and it ran out of space...but I had >2GB when it started...and the backup it made is 27mB??? And now the sdcard is full.
[LG Nitro HD] tdm:
Sounds like you are using dedup. Always use tar, it's more reliable in my experience. There is a setting for that under the backup menus.

The dedup files are under the clockworkmod directory on the sdcard, they are what is taking up all the space. Nuke them with prejudice.
[LG Nitro HD] Flyview:
Awesome! Best developer ever, so prompt. Why would they leave that option as default!?

On another note: would it be a terrible idea to wipe all, install this ROM according to your instructions, but then restore only data from a CM10 nightly or HoNo's hypersonic (cm10)?
[LG Nitro HD] tdm:
Don't know why they left that option in -- presumably it's the new and preferred backup method. But it's unreliable and I won't use it.

You can always dirty flash and/or restore system data from another ROM, but if you do, please don't report bugs that could be caused by doing it. The success you have will depend on how compatible they are. Generally speaking, anything ICS or JB should be pretty compatible. But you may run into issues here and there. If you run into issues, the usual fix is to wipe data for the problem package. For example, the clock usually FC's on boot when going from CM to AOKP. So wipe the clock data to fix it.
[LG Nitro HD] tdm:
Now we're getting somewhere. The CAF version of hardware/qcom/display is being compiled. It seems to require some kernel updates so I'm poking around trying to find those now.

Sigh. Why does qcom always have to update their APIs with each release? :(
[LG Nitro HD] Flyview:
Thanks. I've restored data from HoNo's hypersonic.

The frequency I set with android tuner (cleared data) or even with the phone's performance setting doesn't seem to stick. CPU0 sticks for a little while and CPU1 is reset whenever it goes offline/online. CPU0 might also be resetting when it goes online/offline it just happens less often. What's more concerning is that the max frequency seemingly jumps around to whatever it feels like.

Could this be from the dirty flash?
[LG Nitro HD] tdm:
I don't know ... I haven't really ever investigated the mechanics of these settings.
[LG Nitro HD] hereric:
Hey tdmcode,

I have been getting a TON of screen flickering and enabling "disable hw overlays" seems to rectify the issue.

I was just wondering if there is any way to enable that setting by default? Whenever the phone restarts that setting is disabled, leading to the flickering again.

Thanks for all your work!
[LG Nitro HD] tdm:
Hmm interesting. Some of the VS920 folks are complaining about that also. I've never seen it myself.

I don't know offhand how to make the setting stick, or if it's even possible. Perhaps google search could find an answer?
[LG Nitro HD] tdm:
Looks like I've got CM10.1 building. Not sure if it will boot .. I won't be able to try until tomorrow.

There were two key changes in the kernel that will need to be sorted out: they refactored the ION stuff and, of course, the qcom display stuff. Hopefully that's all the necessary changes to get things working.
[LG Nitro HD] X0dus:
I may be opening a can of worms, but what would stop it from booting other than incompatibilities?
[LG Nitro HD] Flyview:
Alright I'll clear data and see if I'm still seeing the same thing.

Do frequencies for both cores remain at what you set them for you?
[LG Nitro HD] hereric:
What launcher do you use? I just read that it may have to do with apex and nova launcher hiding the notification bar.

I'm on Nova prime
[LG Nitro HD] tdm:
Yeah that is a can of worms lol. Incompatibilities is a pretty broad term that encompasses just about everything.

It will boot far enough to run adb. All that code is pretty standard.

The most likely thing that would keep it from booting into the UI is mismatched qcom display stuff. We have an ICS kernel that has been updated with the JB 4.1 qcom display code. The JB 4.2 qcom display code is (slightly) different from JB 4.1, which is different from ICS (hence my lamentation about qcom updating their stuff every release). This is critical to get right. If the kernel code does not match the user space code, it will crash and the UI won't start.

Now, you're probably not a Linux kernel developer, but there is a hard rule in Linux kernel development: never break the kernel API that is exported to userspace. Only extend it. Android vendors don't give a sh!t about breaking the kernel API. They do it all the time. Qualcomm is just the one I happen to deal with the most...
[LG Nitro HD] tdm:
And here's the failure in the qcom display code:

W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument

E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument

D/qdoverlay( 235): Set pipe=RGB0 dpy=0;

W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument

E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument

E/qdoverlay( 235): Failed to call ioctl MSMFB_OVERLAY_PLAY err=Invalid argument

E/qdoverlay( 235): MdpData failed to play

E/qdoverlay( 235): == Dump MdpData start ==

E/qdoverlay( 235): == Dump OvFD fd=34 path=/dev/graphics/fb0 start/end ==

E/qdoverlay( 235): mOvData msmfb_overlay_data id=2

E/qdoverlay( 235): data msmfb_data offset=0 memid=31 id=0 flags=0x0 priv=0

E/qdoverlay( 235): == Dump MdpData end ==

E/qdhwcomposer( 235): draw: queueBuffer failed for external

E/qdhwcomposer( 235): hwc_set_primary: FBUpdate::draw fail!

E/qdgralloc( 235): fb_post: MSMFB_DISPLAY_COMMIT ioctl failed, err: Invalid argument

E/qdhwcomposer( 235): hwc_set_primary: ctx->mFbDev->post fail!

W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument

E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument

E/qdoverlay( 235): Failed to call ioctl MSMFB_OVERLAY_PLAY err=Invalid argument

E/qdoverlay( 235): MdpData failed to play

E/qdoverlay( 235): == Dump MdpData start ==

E/qdoverlay( 235): == Dump OvFD fd=34 path=/dev/graphics/fb0 start/end ==

E/qdoverlay( 235): mOvData msmfb_overlay_data id=2

E/qdoverlay( 235): data msmfb_data offset=0 memid=31 id=0 flags=0x0 priv=0

E/qdoverlay( 235): == Dump MdpData end ==
[LG Nitro HD] X0dus:
Can of worms, yes, but nothing compared to your following post. lol I get the general 'gist' of what you're saying and extend my thanks to you for being so open of a dev to share your findings like you do and thanks for the continued support of our device.
[LG Nitro HD] DroiDIY:
Every once in a while my phone lags something serious upon waking. Even the power menu barely comes up. I've had this issue before, but only on CM10 ROMs. I've got the CPU clocked down to 1458, (I believe that's the number) screen dithering off, etc, and it's a clean, full wipe install of Beta6. Anyone else have this issue? I haven't noticed any discussion in the various ROM threads I've perused.
[LG Nitro HD] _b_ship:
I'm testing this out for the first time today, very smooth thus far, but does anyone know why Instagram always malfunctions on CM10?
[LG Nitro HD] Flyview:
So I cleared data and cache essentially leaving me with a clean install of quattrimus. I was seeing the same problems. CPU frequencies aren't sticking after reboot (and sometimes even during runtime). This is especially clear for the second core and eventually for the first core as well. The first core likes to end up on 1.67GHz and the second at 1.24GHz.

---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------

Second issue: is there no LTE toggle in mobile settings? How do we turn it off to make sure the phone is not constantly looking for LTE?

Other than these two issues I'm loving it. Feels really smooth.
[LG Nitro HD] woodardbg:
Hey tmcode. How did you root and install recovery for the spectrum? Not much out there for that for the spectrum. My friend has a spectrum with ICS and he's dying to install custom ROMs

Thanks.
[LG Nitro HD] xordos:
Hi want to report back "reboot" issues about beta 6 ( AOKP )

I have been using beta4 and 5 pretty good for some time. But in beta 6, in last 2 days, I have got 3 "reboot", I quote the reboot because:

. When I am in middle of something, twice in game, once in a forum app, the phone suddenly show the "Initiating Swagger" boot animation, then even show "Update 1 of 2 app" if I installed some new app...just like a normal reboot

But:

. The last_kmesg didn't got copied to /data/local/tmp, (the init.d/02kmsg is working, as I can see some backup already there for a real reboot), the /proc/last_kmgs exists and is 2 days old, looks like init.d didn't run

. Also the "uptime" cmd is still showed 2 days right after the "reboot".

Is anyone else got same issue?

Please let me know if I need to do anything to debug this issue, and BTW Thanks tdmcode, this ROM is great.

xordos
[LG Nitro HD] tdm:
Go to AF, they have an active spectrum forum and several great devs. The first thing you need is the bootloader unlocker (pwnage tool), then you can install my rom. But make sure you have a gps lock first, my rom has issues starting up gps on the spectrum that haven't been solved yet.
[LG Nitro HD] tdm:
If the lg logo doesn't come up, it's not a reboot, it's just a ui restart. Get a logcat as soon as possible after you see it do that.
[LG Nitro HD] tdm:
I'll need to look into the cpu frequencies.

Not sure about lte, I don't get lte on straight talk.
[LG Nitro HD] tdm:
Installed v20c baseband, now it says unknown in the about menu. I'll fix that for beta7 on mon/tue.
[LG Nitro HD] lionman229:
Is there no way to switch from lte to hspa+ in this rom? I thought all things from CM10 would be here. If it is I will be installing asap and reporting back frequently!
[LG Nitro HD] tdm:
I don't get lte on straight talk so I can't say. But the build config is very similar to official cm10. If the option is not there, it's surely a small oversight.
[LG Nitro HD] RealyPssd:
When updating from one beta to a newer beta, what's the best way to do it?

I was upgrading from b3 to b6, went to recovery, wiped cache & dalvik and flashed the newer version then rebooted and my Google account wasn't there anymore.

When I went to add an account, Google wasn't listed, only hotmail, Facebook and kobo.

Has anyone else had this happen?
[LG Nitro HD] lordcheeto03:
Did you flash gapps?
[LG Nitro HD] Flyview:
I don't have LTE either. I think the idea is that maybe if we don't turn it off, the LTE radio is on looking for a connection draining the battery.

As for the CPU frequencies, I've looked into it a bit more. Using the stock "set on boot" option in performance settings seems to not work properly. For one, it only sets the frequency for the first core. Secondly, having this option enabled may eventually set the max frequency to a frequency other than that chosen, quite randomly at some time after boot (possibly hours).

I have managed to make frequencies stick for both cores using Android Tuner with the stock CM10 "set on boot" option disabled. However be careful as Android Tuner is a little buggy too. Make sure you have both CPUs online when you click "on boot" to save settings for reboot. I used the init.d method since that sets the frequencies really early and you can check what it will be setting by opening the file created in /etc/init.d/. I'm not sure if the "on boot completed" method works. You set the method in the app settings.