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

Root [UPDATED 8/8/12]Breath of fresh air....an update

Installing update...
assert failed: getprop("ro.product.device") == "VS920" || getprop("ro.product.device") == "VS920" || getprop("ro.product.device
) == "vs920" || getprop("ro.build.product") == "vs920"
E:Error in /sdcard/quattrimus-VS920-cm9-test1.zip
(Status 7)


I downloaded twice same error. I believe it's a build.prop error.
 
megaghostgamer said:
Installing update...
assert failed: getprop("ro.product.device") == "VS920" || getprop("ro.product.device") == "VS920" || getprop("ro.product.device
) == "vs920" || getprop("ro.build.product") == "vs920"
E:Error in /sdcard/quattrimus-VS920-cm9-test1.zip
(Status 7)


I downloaded twice same error. I believe it's a build.prop error.
Click to expand...
bad assert ;)
 
tdm said:
just get me the string please.
Click to expand...

TDM, please don't add the other string. I left it at the LG Nitro string to prevent people from taking from taking updates pushed by LG. I would much rather force people into updating to V6 which would also give them the ability to auto clear the /misc flag.
 
  • Like
Reactions: tdm
Neph81 said:
TDM, please don't add the other string. I left it at the LG Nitro string to prevent people from taking from taking updates pushed by LG. I would much rather force people into updating to V6 which would also give them the ability to auto clear the /misc flag.
Click to expand...

Huh? He's adding that string to make that CWM compatible..
 
megaghostgamer said:
Huh? He's adding that string to make that CWM compatible..
Click to expand...

That version needs to no longer exist. Trust me, I built it as a gateway to get devs in. It was never meant to be a long term solution. People need to update their CWM and this is the perfect reason to. Also, add a prop check for the nitro would allow people to try and flash it onto the nitro and that would also be bad.
 
Neph81 said:
That version needs to no longer exist. Trust me, I built it as a gateway to get devs in. It was never meant to be a long term solution. People need to update their CWM and this is the perfect reason to. Also, add a prop check for the nitro would allow people to try and flash it onto the nitro and that would also be bad.
Click to expand...

Oh lol.. Well it did good for me until CM9. :)
 
Under keyboard input in the test run it says Android keyboard English... But under dev tools it shows in package details as Latin.... Could that cause the keyboard to not show up possibly because it's looking for a version that doesn't exist....
 
atomilluminati said:
Under keyboard input in the test run it says Android keyboard English... But under dev tools it shows in package details as Latin.... Could that cause the keyboard to not show up possibly because it's looking for a version that doesn't exist....
Click to expand...

I think the problem is that the input system thinks that one of the input devices is a physical keyboard. But I haven't tracked it down yet.
 
I tried a BT keyboard, hacker's keyboard.apk, and a usb keyboard. Nodda on any of them. This thing is fluid smooth thou and I have a feeling it will only get better.
 
It's a finicky keyboard (logitech MX5000) and while the phone found it and paired up, the connection would constantly die. The few times it stayed connected, nothing would come up. If someone has a newer BT keyboard that they would like to try, I would be interested in the results.
 
just a thought.... here is a how the configuration looks from developer tools in plagued

Fontscale= 1
hardkeyboardhidden= 2
keyboard= 1
locale= en_us
mcc= 0
mnc= 0
navigation= 1
navigationhidden= 2
orientation= 1
screenlayout= 0X10000022
touchscreen= 3
uimode= 0X11

displaymetrics

density= 2.0
densitydpi= 320
heightpixels= 1280
scaleddensity= 2.0
widthpixels= 720
xdpi= 320.8421
ydpi= 318.7451
Click to expand...

this is what the configuration in developer tools from cm9 looks like

Fontscale= 1
hardkeyboardhidden= 1
keyboard= 2
locale= en_us
mcc= 0
mnc= 0
navigation= 2
navigationhidden= 1
orientation= 1
screenlayout= 0X10000022
touchscreen= 3
uimode= 0X11

displaymetrics

density= 2.0
densitydpi= 320
heightpixels= 1280
scaleddensity= 2.0
widthpixels= 720
xdpi= 326.57144
ydpi= 328.40405
Click to expand...

not sure if these settings make a difference or not but there is some differences and i figured because they work in plague with this setting in place that it might correct whatever issues we are having in cm9's keyboard issues
 
Keyboard 2 might be the issue. This phone is anything but easy and it *should* allow the screen keyboard to work with no work.... It's the hard keyboards like on the Moto droids that cause issue, usually.
 
I think disabling CONFIG_ATCMD_VIRTUAL_KBD in the kernel config fixes the keyboard.

I don't have time to build and push a new ROM, so I posted just the boot.img at getquattrimus.com. md5=5ced3fb84297deaa393e0b37486fb54a.

To use it:

adb shell mount -o remount,rw / /
adb push boot.img /
adb shell dd if=/boot.img of=/dev/block/mmcblk0p8 bs=4096
adb shell sync
adb shell reboot

Now I think we're down to the radios and cameras. Yay! :D
 
Flashed the test rom this morning for a few minutes and it was exciting to see ics on my spectrum. One issue I found is screen shots won't capture. It said the storage wasn't accessible.

Edit: one other thing that didn't work for me was the home soft key.
 
I'm gonna test this later tonight. I gotta get my fascinate back stable to use as my phone so I can try to get us some roms made. But I'm not releasing anything until cm9 is solid. And with the amazing progress these guys have made. It'll be no time before we have an amazing phone


tdm said:
I posted just the boot.img at getquattrimus.com
Click to expand...

http://getquattrimus.com/roms/quattrimus/VS920/
i had to poke around to find it.. so heres a link
 
You must log in or register to reply here.
Back
Top Bottom