-
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)
- Thread starter tdm
- Start date
-
- Tags
- lg spectrum
scottfan81
Member
tdm
Android Expert
Here goes nothing ...
rc5 is up. I hope this is "offifcial CM quality" (or even better), with the exception of the wifi-p2p client reboot bug (tracker issue 4).
quattrimus-iproj-cm10-rc5.zip md5=0284eaa17364cbbe8740e8961c82d435
quattrimus-iproj-aokp41-rc5.zip md5=ae489cbf06a27e6948bf454ecb2738d0
Changes from rc4:
1. Use GB version of GPS blobs.
Works great on ZV4, need ZV7 feedback.
2. Add support for build_id 8660-AAABQNBYA-362421 as VS920.
Still not sure exactly what .cab and/or vendor rom this came from, but beddybeezy says that's his build_id.
3. Auto wipe script.
If the vendor and major/minor versions match, do nothing. If they don't, wipe system data and dalvik cache(s).
Vendor and major/minor versions would be eg. AOKP 4.1 or CM 4.2. Point version is ignored.
In no case should user app data ever be touched.
4. Install time scripts don't get put onto the phone.
backuptool.sh, modelid_cfg.sh, autowipe.sh, and a couple others are only used at install time. They don't get put into /system any more.
5. AOKP41: addon.d support. This keeps gapps and /etc/hosts between flashes, even if you do a full wipe.
6. CM10: don't run modelid_cfg.sh.
Indeed, it's not even in the zip anymore. This is harmless but it's not for our phones so don't do it.
rc5 is up. I hope this is "offifcial CM quality" (or even better), with the exception of the wifi-p2p client reboot bug (tracker issue 4).
quattrimus-iproj-cm10-rc5.zip md5=0284eaa17364cbbe8740e8961c82d435
quattrimus-iproj-aokp41-rc5.zip md5=ae489cbf06a27e6948bf454ecb2738d0
Changes from rc4:
1. Use GB version of GPS blobs.
Works great on ZV4, need ZV7 feedback.
2. Add support for build_id 8660-AAABQNBYA-362421 as VS920.
Still not sure exactly what .cab and/or vendor rom this came from, but beddybeezy says that's his build_id.
3. Auto wipe script.
If the vendor and major/minor versions match, do nothing. If they don't, wipe system data and dalvik cache(s).
Vendor and major/minor versions would be eg. AOKP 4.1 or CM 4.2. Point version is ignored.
In no case should user app data ever be touched.
4. Install time scripts don't get put onto the phone.
backuptool.sh, modelid_cfg.sh, autowipe.sh, and a couple others are only used at install time. They don't get put into /system any more.
5. AOKP41: addon.d support. This keeps gapps and /etc/hosts between flashes, even if you do a full wipe.
6. CM10: don't run modelid_cfg.sh.
Indeed, it's not even in the zip anymore. This is harmless but it's not for our phones so don't do it.
beddybeezy
Member
I dont know why my phone is different but I loved rc3 but it didnt have data. So i appreciate the help and what you've done tdm and others!
tdm
Android Expert
By that did you mean using the file you posted here? Or did I miss the blob?
rc5 has a complete GB GPS setup. All the gps libraries and gpsone_daemon. That should resolve the logspam that Neph81 reported. If it works for ZV7 users, we'll call that issue resolved and push for official CM support. If not, well, it's going to be painful.
tdm
Android Expert
The auto wipe script will not do anything if you are flashing the same vendor/version as is currently installed.
The auto wipe script will only wipe data for system apps and dalvik cache if you are changing the vendor/version from what is currently installed.
If you wish to disable auto wipe completely, you may create a file named /sdcard/.noautowipe (contents are irrelevant, only its presence is checked).
BTW, still waiting for GPS feedback from ZV7 users that had GPS on earlier builds...
ortrigger
Android Expert
Exactly. It will wipe if you are coming from a completely different rom but won't if you're just upgrading to a newer version.
beddybeezy
Member
tdm i just tried to install rc5 and it did the same thing...if i can recall you removed the i_lgu thats the model the error message is telling me i have that might be why i could install cm10 rc3 because it still supported it
tdm
Android Expert
It still says i_lgu? Strange... I'll take a look.
tdm
Android Expert
I think the build beat me to the change on cm10. I'll redo that for the next build. Try aokp41 and see if it works.
EDIT: had it backwards.
beddybeezy
Member
i tried cm10...should i try aokp
tdm
Android Expert
Yeah I got that backwards.
beddybeezy
Member
yes aokp works thank you!
Sorry that I didn't see this before. Yes, there is a good chance that this could help us. They seem to be calling out hardware decoding/encoding natively in the Rom with these changes. Only a full build would be able to tell how effective it is as there are most likely changes in OMX that the did as well.
tdm
Android Expert
Sweet, now I'll start a serious conversation with rmcc and jeagoss about what it takes for official support. Likely just pushing some commits for kernel and device trees, and handing the vendor libs to them.
First reboot (dirty flash I guess... from cm10 rc4 to cm10 rc5) - phone running INCREDIBLY slow, no cell data coverage, no GPS. only wifi; wouldn't reboot. Finally held the power button until it shut off, then turned back on and everything is great! 4G, GPS, etc...