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

I ran aokp41 from the start but was always experiencing performance issues with it so switched over to CM10 and it runs much smoother for me. At first I missed the extra features of AOKP but over time not as much. I get bored though and switch back and forth but since beta 5 of aokp I get the roaming signal by my signal bars and when I plug my bose desktop speakers into my phone the phone goes into silent mode, and even when I toggle it out of silent mode after a couple minutes it turns itself back on.

I've posted this twice already and my post have been completely ignored by everyone. I'm confused as to how I can be the only one this is happening to. I have neither of these issues with CM10 beta 5 and 6.

So could someone on AOKP beta 6 plug a set of speakers into their phone and see if it goes into silent mode please.

And could someone please give me some input on why my phone keeps showing as roaming (though it's actually not, data works fine) and how I might fix it since it seems I'm the only one this is happening to.


i have the same roaming and silent mode issue. I started to get screen flickering in aokp41b6 as well. when the screen shuts i also get a few extra clicks
 
I'm gonna fix the baseband string. Can someone post the output of this command on pastebin:

strings -n 12 /system/etc/firmware/misc_mdm/image/amss.mbn

Thx!
 
Hope this is what you need TDM - Pastebin.com

Yes that is great, thanks. I think I'll use this string: VS920Z_V7_15

Background:

The RIL is responding with an error when requesting the baseband version on all iproj models (VS920, P930, etc.) I tried to coerce the RIL into giving up the baseband string for some time today but was unsuccessful.

CM worked around this by extracting the string from the modem firmware partition. But their code only works for the GB baseband on the P930.

I noticed that the modem firmware partition is a VFAT filesystem mounted on the path I mentioned, and amss.mbn is one of two or three files that contains the desired string on my P930. It seems to contain a usable string on the VS920 also.

The string above is not exactly in the desired format. It is the start of a line which reads:

VS920Z_V7_15, 362421, Jun 18 2012, 15:28:10

But I can chop off everything after the comma. That will be close enough for now.
 
@devs:

There is a thread in the Nitro section on XDA that has flashable baseband files. These appear to simply write out to mmcblk0p1 and mmcblk0p14. It's highly likely that the same could be done for the Spectrum, so that users could switch between ZV4, ZV6, and ZV7 basebands.

Anyone want to take that up?

Here's their META-INF/com/google/android/updater-script:

ui_print("Installing baseband...");
package_extract_file("baseband.img", "/dev/block/mmcblk0p14");
ui_print("Installing firmware...");
package_extract_file("firmware.img", "/dev/block/mmcblk0p1");
 
nayr,

There was a lib fix posted in an earlier post that solved this problem on earlier versions...it might have been left out in beta6, or it somehow didn't replace when you flashed. I had the same problem, so I grabbed the lib file and replaced the faulty one using es file explorer and everyone said they could hear me clear again.

I'll take a look at that, sorry.
 
No idea. Perhaps someone could give me the string that stock displays and a copy of the two baseband partitions?
Baseband Version:
VS920ZV7-M8660A-AABQNSZM-3.6.2421

mmcblk0p1 and mmcblk0p14 dumps: http://db.tt/1ASAE8fI

output from 'strings -n 12 mmcblk0p1.img' (this is where the baseband string is)
http://db.tt/Xgs3cIOy

output from 'strings -n 12 mmcblk0p14.img'
http://db.tt/SY7Kh1Ea

1970-01-10%2006.07.05.png
 
  • Like
Reactions: tdm
Okay I have all I need to fix the baseband string and create flashable baseband images for ZV4 and ZV7.

If anyone is on ZV6, or is willing to put it on their phone temporarily, please reply with a copy of mmcblk0p1 and mmcblk0p14 like d2a just did above, so that I can make a flashable baseband and verify that my string extractor works on it.

Thanks!
 
Okay I have all I need to fix the baseband string and create flashable baseband images for ZV4 and ZV7.

If anyone is on ZV6, or is willing to put it on their phone temporarily, please reply with a copy of mmcblk0p1 and mmcblk0p14 like d2a just did above, so that I can make a flashable baseband and verify that my string extractor works on it.

Thanks!

If no one gets it for you today I'll flash back to it tonight and post it for you.
 
Ok this is awesome that you guys are getting close to perfecting the jelly bean 4.1.2 for this phone but there is one thing that happens a lot to me on every version of beta so far and its the blue flash.

Sometimes it just does it randomly and sometimes only on the notification shade. Secondly the screen flashes a lot when I'm in the lock screen and I pull down the shade.

Is this just happening to me or are there any other people who have this issue and also is there a known fix
 
Ok this is awesome that you guys are getting close to perfecting the jelly bean 4.1.2 for this phone but there is one thing that happens a lot to me on every version of beta so far and its the blue flash.

Sometimes it just does it randomly and sometimes only on the notification shade. Secondly the screen flashes a lot when I'm in the lock screen and I pull down the shade.

Is this just happening to me or are there any other people who have this issue and also is there a known fix

It's common to all the iproj phones (VS920, P930, etc.) it seems like only some phones do it, others don't. Unfortunately neither my P930 nor VS920 does it so I can't really debug it.
 
It's common to all the iproj phones (VS920, P930, etc.) it seems like only some phones do it, others don't. Unfortunately neither my P930 nor VS920 does it so I can't really debug it.


Mine does occasionally. What would I need to look for to find what's causing it?
 
Ok this is awesome that you guys are getting close to perfecting the jelly bean 4.1.2 for this phone but there is one thing that happens a lot to me on every version of beta so far and its the blue flash.

Sometimes it just does it randomly and sometimes only on the notification shade. Secondly the screen flashes a lot when I'm in the lock screen and I pull down the shade.

Is this just happening to me or are there any other people who have this issue and also is there a known fix

I know phillip complained about this issue. I thankfully don't have this issue but I did experience terrible screen flicker and studder on stock ICS but since cm9 I haven't been having this issue. There have been times when I'll get a minor flicker but it's never bad and doesn't hapen often and is never blue. I would flash back to stock and complain to verizon about the phone being defective and get a replacement. Maybe a new one will work better.
 
Ok this is awesome that you guys are getting close to perfecting the jelly bean 4.1.2 for this phone but there is one thing that happens a lot to me on every version of beta so far and its the blue flash.

Sometimes it just does it randomly and sometimes only on the notification shade. Secondly the screen flashes a lot when I'm in the lock screen and I pull down the shade.

Is this just happening to me or are there any other people who have this issue and also is there a known fix

Almost forgot... try disabling hw overlays in the development options and see if that helps.
 
GPS still kinda funky for me.. I can lock on to the satellites initially, but in the course of a 25 minute drive, it lost signal 5 times and battery dropped from 65 to 33.

Is this kind of performance normal? Or is it time for another replacement from Verizon.
 
GPS still kinda funky for me.. I can lock on to the satellites initially, but in the course of a 25 minute drive, it lost signal 5 times and battery dropped from 65 to 33.

Is this kind of performance normal? Or is it time for another replacement from Verizon.

I will agree with you that my GPS has been kinda iffy. I flashed the new baseband though yesterday so maybe that will fix it.

Also recently I have noticed that my battery dies really quickly now. I usually use the deep sleep battery saber but I wanted to try it without it and the battery life died extremely quickly.
 
GPS still kinda funky for me.. I can lock on to the satellites initially, but in the course of a 25 minute drive, it lost signal 5 times and battery dropped from 65 to 33.

Is this kind of performance normal? Or is it time for another replacement from Verizon.

I had this issue the other day when I was using GPS with moderate cloud coverage in an area with very weak cell signal... that was it for me tho.
 
Back
Top Bottom