• 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)

thank you TDM and all developers who made this possible!! This was the first time i attempted to flash a phone, let alone my daily driver. I was a little apprehensive with all of the comments about GPS not working and radio signal not functioning properly. Honestly i thought i was going to brick my phone, but the thought of running JB 4.1 was worth the risk. I'm happy to say that everything worked out!!! GPS, phone signal (3G-4G), and WIFI! haven't tried blue tooth yet, but i never use it anyway. in the process now of recovering all my apps and personalizing my new device :)
The only issue i had was backing up my contacts and sms messages. Titanium backup locked up once it reached my contacts for some reason... but its a minor gripe, especially considering this is my first time doing this and it worked out so well for me!

Thanks again for such a well put together forum and a damn good community of individuals! I just wish that i was on the technical level of you guys to somehow contribute something back... thanks again, i havent been able to put my phone down for hours!

welcome to the world of rooting and custom roms, you'll never look back from here, and soon will begin to look at people funny who run stock on android. :p
 
thank you TDM and all developers who made this possible!! This was the first time i attempted to flash a phone, let alone my daily driver. I was a little apprehensive with all of the comments about GPS not working and radio signal not functioning properly. Honestly i thought i was going to brick my phone, but the thought of running JB 4.1 was worth the risk. I'm happy to say that everything worked out!!! GPS, phone signal (3G-4G), and WIFI! haven't tried blue tooth yet, but i never use it anyway. in the process now of recovering all my apps and personalizing my new device :)
The only issue i had was backing up my contacts and sms messages. Titanium backup locked up once it reached my contacts for some reason... but its a minor gripe, especially considering this is my first time doing this and it worked out so well for me!

Thanks again for such a well put together forum and a damn good community of individuals! I just wish that i was on the technical level of you guys to somehow contribute something back... thanks again, i havent been able to put my phone down for hours!

Thanks, that made me smile. Reminds me of my first custom Rom install on my old OV. :)
 
Wasn't aware of licensing issues and everything.. Glad that got cleared up before I wasted some time making the thing.. And here I was thinking I would be the great one to do this ingenious thing first..
 
thank you TDM and all developers who made this possible!! This was the first time i attempted to flash a phone, let alone my daily driver. I was a little apprehensive with all of the comments about GPS not working and radio signal not functioning properly. Honestly i thought i was going to brick my phone, but the thought of running JB 4.1 was worth the risk. I'm happy to say that everything worked out!!! GPS, phone signal (3G-4G), and WIFI! haven't tried blue tooth yet, but i never use it anyway. in the process now of recovering all my apps and personalizing my new device :)
The only issue i had was backing up my contacts and sms messages. Titanium backup locked up once it reached my contacts for some reason... but its a minor gripe, especially considering this is my first time doing this and it worked out so well for me!

Thanks again for such a well put together forum and a damn good community of individuals! I just wish that i was on the technical level of you guys to somehow contribute something back... thanks again, i havent been able to put my phone down for hours!


This is only the second time I have put a ROM on my phone. First one was BP from PG. I have installed the AOKP41 ROMs as they have been updated. I TRULY appreciate the hard work that has gone into this ROM and I love the community that is testing and developing this ROM. I am currently on AOKP41 Beta4 and LOVE IT.:D This has made owning this phone so much more fun.
 
***EDIT***

Nevermind guys, im an idiot, i forgot that i can just dial the number for my voicemail... whoops. the level of noobie-ness in me is strong.


one thing that i ran into today was that i noticed im missing my voicemail lol. i backed it up before i wiped my phone, but when i attempt to restore it (voicemail 2.1) Titanium backup hangs. is there some sort of quick fix for this or am i screwed? im stationed on an army base and the building that i work in all day blocks service, so voicemail is pretty important. thanks again gentlemen!
 
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.
 
Hey everyone. Just wanted to document this in case it helps anyone out. First of all, tdm and all others involved thank you so much for this rom! Really a great piece of work! I'm currently on AOKP Beta 5 and absolutely loving it. Okay, onto the gritty stuff.

Okay, even after reading about all the GPS stuff I thought to myself, "Well I have mine on and I'm running a V7 rom (Icy Fusion) and I also have my GPS on and it locks fine...so I should be good." All went well, and surprisingly my GPS was working great. Then as I went about my business installing and customizing the phone, suddenly it just stopped working at some point along the way (not exactly sure when). I've come to the conclusion it was probably because I didn't come from a stock v7 rom when I verified I had lock.

Anyways, I may try it again but while researching a bit I just wanted to link this post here from the official cyanogenmod repo as I believe it may shed some light on what's going on (I think?). Here's the link for those interested in it: Gerrit Code Review

Sounds like something is actually locking the GPS device and it's sticking through the flash? Marked as fixed though in their repo as of a few days ago.

Okay, onto the next point I wanted to mention. Everyone has been saying the JB camera hasn't worked for them. Somehow, mine works fine. I've taken pictures, recorded 720p and 1080p video as well as played it back with the video player. I just now tried pressing the power button while in the camera app and everything functions normally (aka no reboot). Screen shuts off as per the norm and when I turn it back on I'm back in the camera app. There have been a few quirks that I noticed in there though I wanted to document as well.

While recording 1080p video, one time I noticed the image actually "looped" vertically very slowly. The bottom slowly moved up to the top simply repeating the view of the camera again. Strange. I tried reproducing it and I wasn't able to. I also noticed that I've gotten different options in the camera mode randomly before. One time I went in there and I had options for the picture ratio (VGA or SXGA). The next time I went in there (probably after I'd rebooted at least once) it wasn't there. Camera app, overall, is a bit odd. Is the area where the camera's button a large rectangle that takes up a good 1/4 of the screen for everyone else?

Anyways, just wanted to report those things to the forum just in case the link may help anybody or my experiences may trigger an "ah ha" moment in a dev. :) Once again, thanks to everyone involved with this rom as it's the best I've seen on this device thus far! Let me know if anyone has any questions or needs any further info from me. Would love to help out any way I can.
 
  • Like
Reactions: tdm
Put simply, if your software (android) turns gps on, that hardware stays on if you flash a new rom. Vice versa, that's why it won't turn on if you don't toggle it with stock first. It's been that way for as long as I can remember and I think it's only gps that toggles independent of the OS... Probably related to the old gps/9-1-1 requirements.

There's something in the cm code that isn't properly toggling the hardware.
 
On AOKP beta5

No 4g problems
No GPS problems
Very smooth scrolling (once I edited my animation scales to .5)
No random reboots

The only issue I am having, which seems to be unique to my device, is voice recognition. My microphone works and the circle changes sizes when I speak, but it seems like it's not even trying to convert speech to text (see screenshot). Using speech-to-text from the keyboard shortcut is hit or miss - it either skips words I say or fails outright. I have tried personalized voice recognition on and off with no change. The proper language is selected. I don't get any FC's or anything, it just times out and says "tap to speak"

I'm only mentioning this here because AOKP beta3 and beta5 are the only Spec roms I have experienced this with (I have not tried CM betas). Perhaps I got a bad gapps dl? I used the one from the OP link - but could there have been an issue with the dl? I mean I am seriously not experiencing any other issues with this ROM.

Aside from reflashing a new gapps dl (which is just a wipe dalvik/cache then flash, right?) what other steps could I take?

Thanks for any input and for all of y'all devs hard work.

mic.png
 
***EDIT***

Nevermind guys, im an idiot, i forgot that i can just dial the number for my voicemail... whoops. the level of noobie-ness in me is strong.


one thing that i ran into today was that i noticed im missing my voicemail lol. i backed it up before i wiped my phone, but when i attempt to restore it (voicemail 2.1) Titanium backup hangs. is there some sort of quick fix for this or am i screwed? im stationed on an army base and the building that i work in all day blocks service, so voicemail is pretty important. thanks again gentlemen!

Should be able to just press and hold 1 on the dialpad? My Speed Dial for 1 has always been automatically set to voice mail.
 
***EDIT***

Nevermind guys, im an idiot, i forgot that i can just dial the number for my voicemail... whoops. the level of noobie-ness in me is strong.


one thing that i ran into today was that i noticed im missing my voicemail lol. i backed it up before i wiped my phone, but when i attempt to restore it (voicemail 2.1) Titanium backup hangs. is there some sort of quick fix for this or am i screwed? im stationed on an army base and the building that i work in all day blocks service, so voicemail is pretty important. thanks again gentlemen!

Does the phone dial voicemail properly, eg. when you have a message? That should work. It's a compile setting.

Hmm ... I don't see it in the build tree. Let me investigate.
 
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.
How dare you have a life outside tweaking/recompiling for us crack flashers!

Thanks again for all you (and Neph and others) do!
 
this rom is good but i think im going back to stock just because the blue flash ive been getting is annoying me. its getting worse. i get it probably every 30 minutes now. and to me the battery is way worse than stock.
 
one thing that i ran into today was that i noticed im missing my voicemail lol. i backed it up before i wiped my phone, but when i attempt to restore it (voicemail 2.1) Titanium backup hangs. is there some sort of quick fix for this or am i screwed? im stationed on an army base and the building that i work in all day blocks service, so voicemail is pretty important. thanks again gentlemen!


I have noticed that sometimes when titanium hands during a restore (make sure to only do restore data, it works better sometimes), let it sit while hung for a good 15-30 minutes, then use Rom toolbox or the built in system task manager to force close titanium. After that, reboot, and "sometimes" it will have successfully completed the restore, even though you force closed it.




Okay, onto the next point I wanted to mention. Everyone has been saying the JB camera hasn't worked for them. Somehow, mine works fine. I've taken pictures, recorded 720p and 1080p video as well as played it back with the video player. I just now tried pressing the power button while in the camera app and everything functions normally (aka no reboot). Screen shuts off as per the norm and when I turn it back on I'm back in the camera app. There have been a few quirks that I noticed in there though I wanted to document as well.

While recording 1080p video, one time I noticed the image actually "looped" vertically very slowly. The bottom slowly moved up to the top simply repeating the view of the camera again. Strange. I tried reproducing it and I wasn't able to. I also noticed that I've gotten different options in the camera mode randomly before. One time I went in there and I had options for the picture ratio (VGA or SXGA). The next time I went in there (probably after I'd rebooted at least once) it wasn't there. Camera app, overall, is a bit odd. Is the area where the camera's button a large rectangle that takes up a good 1/4 of the screen for everyone else?


two comments from here (I know the reboot from the camera app was fixed, and no I have not flashed that update), just wanted to note that it does not have to be in the camera app, it is any time the camera is active. Face unlock and Google chat video calls reboot the phone if you press the power button while the camera is active. (Only reason I will ever update from cm10 b3) this is truly annoying when I turn my screen on to check the time, then turn it back off...

And yes I freaking hate the camera app ui layout, more ******ed than having a three button selection area that pops up three buttons when you press it, instead of just selecting what you pressed, is the 1/4 screen taken up by the shutter button that nearly every other app has as a transparent overlay on the image. I am happy it works though, and I went back to using procapture paid version because of this.




On AOKP beta5

No 4g problems
No GPS problems
Very smooth scrolling (once I edited my animation scales to .5)
No random reboots

The only issue I am having, which seems to be unique to my device, is voice recognition. My microphone works and the circle changes sizes when I speak, but it seems like it's not even trying to convert speech to text (see screenshot). Using speech-to-text from the keyboard shortcut is hit or miss - it either skips words I say or fails outright. I have tried personalized voice recognition on and off with no change. The proper language is selected. I don't get any FC's or anything, it just times out and says "tap to speak"

Nothing I use has a moving acknowledgement of recording any sound, but works great, again, still on cm10 b3. One exception, I downloaded a pair of graphical audio analyzer apps to test, and both correctly show sounds being picked up by the Mic, so I have no idea why any voice dictation app, sound hound, nor viggle show any motion during sound recording.

Figured it was just another unique situation to my device.

Either way, still loving cm10.

Not trying to make this any longer, but...

@TDM
My phone was sitting in the couch fit a good two hours, not being used, I picked it up and put it on my end table. The screen did NOT power on, and about 3 seconds after I set it down, it rebooted (full reboot, LG logo and all). do you want the kmsg?
 
@TDM
My phone was sitting in the couch fit a good two hours, not being used, I picked it up and put it on my end table. The screen did NOT power on, and about 3 seconds after I set it down, it rebooted (full reboot, LG logo and all). do you want the kmsg?



i just had the same problem earlier today but mines didnt reboot. the screen was on but it was in a black screen. so i had to pull the battery
 
@TDM
My phone was sitting in the couch fit a good two hours, not being used, I picked it up and put it on my end table. The screen did NOT power on, and about 3 seconds after I set it down, it rebooted (full reboot, LG logo and all). do you want the kmsg?

Yes please upload the last_kmsg. Thx!
 
For anyone holding out, I've been on CM10 B5 since before the OP was updated and not having any issues with it. GPS solid. Google Now (including voice commands) works. No bluetooth related reboots. Only thing left is the cpufreq and it sounds like TDM's on the trail of that.

On the cpufreq issue, has anyone noticed it happening more or less on any particular schedulers?
 
Voice search uses the phone mic... I have no issues with the recognition.

@Travesty: wipe data and cache when flashing a rom... Wiping data removes all user apps and all the settings/data that may have gone corrupt since the initial flash.
 
Looked at the CM10.1 change found my pantherts earlier today (thanks again!) They seem to be using a custom libloc, version 50001, instead of the "standard jb" libloc. Don't know where it came from or why. The code is radically different so the patches don't apply. However, the "standard jb" code does seem to include the privacy flag stuff, so perhaps this issue was specific to newer qcom code? I thought about compiling and using their stuff but I'm not expecting it to work.

Tried a quick test for GPS .. copied over the GB libs and gpsone_daemon blobs from GB (from the Eclipse ROM). No dice there either. That is probably not a big deal, though. If I used the GB libs, that might require a vendor GB prior to flashing JB, and few phones seem to be in that situation anymore. Requiring a vendor ICS prior to flashing JB seems to be reasonable and much more common.
 
Looked at the CM10.1 change found my pantherts earlier today (thanks again!) They seem to be using a custom libloc, version 50001, instead of the "standard jb" libloc. Don't know where it came from or why. The code is radically different so the patches don't apply. However, the "standard jb" code does seem to include the privacy flag stuff, so perhaps this issue was specific to newer qcom code? I thought about compiling and using their stuff but I'm not expecting it to work.

Tried a quick test for GPS .. copied over the GB libs and gpsone_daemon blobs from GB (from the Eclipse ROM). No dice there either. That is probably not a big deal, though. If I used the GB libs, that might require a vendor GB prior to flashing JB, and few phones seem to be in that situation anymore. Requiring a vendor ICS prior to flashing JB seems to be reasonable and much more common.

Yeah, I wasn't quite sure if the code was 100% applicable but I did notice that the privacy lock stuff appeared in earlier logs that Neph had posted way earlier in this thread. That's what really caught my eye and I remembered that log that Neph had posted and thought there may be some common denominators there.

Also, I ended up loading up the V7 cab on my phone and then restored my nandroid of AOKP Beta 5. GPS lock is all good now for me.
 
dirty flashed aokp41 b5 over b4. lost gapps, wiped cache, installed gapps. had a hiccup, rebooted ... all good. data seems to be staying this time around for me.
 
Just curious, my wife's spectrum is running broken out and she wants aokp 41 like mine has.. would I have to return her phone to stock and take the ICS OTA or .cab followed by using the bootloader tool, or can it be flashed straight from broken out?
 
Back
Top Bottom