karendar

Well I have good news and bad news... The good news is it compiled! The bad news is... Wireless doesn't work!

I'll get back to you in a bit.

karendar

AGREED! Wait... What?

damien1114

Lol. Stupid WiFi

karendar

Check first post.

jparasite

The permission for /system/bin/screenshot isn't being set after an install, mostly because of the pre-generated updater-script not accounting for it.

In /META-INF/com/google/android/updater-script, after this line:
set_perm(0, 0, 0777, "/system/bin/dtinstall");

Add the following:
set_perm(0, 0, 06755, "/system/bin/screenshot");

I manually changed the permissions after a fresh install R4 and screenshot now works.

karendar

Great, I'll fix that in a jiffy!

Otherwise is R4 working good for you guys?

jparasite

Overclocking works awesomely, looks good so far. Haven't had alot of time to test out if everything works but great job on the OC.

karendar

Adding the new Adreno drivers helped the phone, but OC'ing helps it even more! I'm able to run TSF Shell with very little lag... Which is surprising to me.

I found out two new things for the ROM:

1) LG sucks badly when it comes to market compatibility for their devices. I can in no way get the phone to install some apps I KNOW run well on the phone (Do not show up in market, when I do find the link in market, says it's not compatible with my device). To test this, try installing Soundhound or shazam. If it works for you, must be my phone which is messed up.

2) The reason auto brightness doesn't work is because LG brilliantly destroyed the light sensor driver. Lux values returned by the phone is always -1, meaning no data is returned from the sensor... Will have to kang work from another phone to re-enable light array.

jparasite

This weekend I'll actually have time to d/l 2.3.3 sources from Google and actually attempt a git-merge of V20B sources. If we can compile the framework from scratch, I will have a better time of porting over CM7 features using actual code.

I'm a much better programmer than modder haha.

karendar

I'm apparently the polar opposite! Great modder/cook, horrible programmer! hehe

damien1114

Im gonna attempt to flash this to my phone after I back up all my apps >.>

karendar

Just so you know, if you have any issues after flashing, you might have to upgrade the phone to v20b manually so it updates the baseband... Keep me posted if everything works out.

Also, if you wait before downloading it, I'll update so the screenshot app works.

BabblingCamel

Just flashed R4 successfully. I'll update if I come across any bugs.

jparasite

karendar, you may want to update your main post with new recovery information (now that we have CWM 5.5.0.4).

cjmaniac

I've been running v4 now for a couple days and no issues so far. Just wondering what settings everyone is running for good balance of performance/battery life in setcpu?

damien1114

Stupid question but can someone tell me how to update to the new Gingerbread and how to root it? I cant remember >.>

nitramus

I am having problem with your rom. At first I had jiilik's version and had the dalvic cash issue so I tried karendar's and would keep reebooting by it self so I went back to jiilik.
Now I amd still trying karendar but I am still having the dalvic cash just like with jiilik.

I did wipe averything "all data/factory reset" and also Data, cash sdcard/.android_secure, system, dalvic-cash each separately.
Probably overkill but better safe then sorry.

I understand that wiping /system removes it all so I reinstall the rom, do factory reset. I install a few basic apps and reboot often and after a while the dalvic cash problem just come back again.

I have the latest software v20b

Last edited by nitramus; August 10th, 2012 at 09:29 PM.

damien1114

I have the same problem. What I suggest is using DarkTremors app2sd witch is built into the rom.

karendar

Hey guys,

I actually think there's an issue with the ROM, but I just got back from vacation, so I can't fix it for now. The issue is the ROM is a little too big and /system gets filled up, thus causing possible issues.

Here's what I recommend you try:

- Use WinRAR or 7zip, open the ROM's zip file.
- Move the following files from the system folder to the data folder (or delete them): Maps.apk, thinkdroid.apk, gmail.apk, youtube.apk
- Reflash this modified file

This'll move the files to your data folder, so keep in mind it'll gobble up some space. Considering that the ROM has app2SD, I suggest using that. You need an ext4 or ext3 partition on your SD card to use it of course.

jiilik

Hey thanks! Glad to see you folks are still working on this.

karendar

Glad to see an old modder checking in. I was really motivated about having your custom kernel on v20B... So I read up on how to compile kernels and let me tell you it's pretty easy to do! Now I have to figure out how to fix liblights.

androidwkim

Whenever I try to download something on market, the phone resprings (sorry, don't know what the android term would be) and so I can't download anything. Is that part of the play market issues you mentioned in your post? I'm still on the old market because it won't let me download or upgrade anything.

Otherwise, thanks for the amazing tweaks, the phone feels fast now.

Some more info: The kernel is the right version (says Karendar) but the software version is still at v20a.

Last edited by androidwkim; September 3rd, 2012 at 07:27 PM. Reason: EDIT: It's not when downloading apps, its when I try to install anything.

karendar

Software version is just a string I forgot to modify, you can ignore that. I'll fix it eventually (Next release). As for market issues, I have none here so I can't really say what's going on. Do you know how to pull a logcat? Get the application alogcat and get me a log of what's happening, might be able to see if it's ROM related or something wrong with your phone.

Otherwise, have you tried to clear market data through settings/applications? Or do a factory reset?

I know I've had some issues updating to the latest Vendor.apk on my ROM... But doesn't stop anything from working on my end.

Before upgrading the ROM, did you flash stock V20B?

androidwkim

Ahhh.... Now I see what's wrong, lol. The phone is still on v20a for some reason. I restored my nandroid backup and checked the settings, it's gingerbread 2.3.3 but the software version is still v20a. I thought it was v20b before I flashed anything, but I guess I was mistaken. Is that what's causing the problems?
How can I update to v20b?

karendar

You have two methods of proceeding. You can either use the LG update software which has been known to cause issues with some, or you can use the KDZ firmware update software supplied in the "Foolproof guide to restore a bricked SHine plus" thread posted by seanre453. I suggest using the foolproof guide if you're a little tech savvy as it works great and avoids having issues with lost data link during flash from the LG update. To get the V20B ROM, grab it from here:

http://csmg.lgmobile.com/swdata/WEBSW/LGC710H/ATLSBK/V20b_00/V20B_00.kdz

You can find the foolproof guide in the all things root thread. Once the phone is updated to v20B, you have to root again and flash custom recovery and then flash my ROM over.

androidwkim

I checked the LGMobile Support tool and it says that 20a is the most recent version, so it looks like I'll have to go the custom route.

So I can just follow the instructions starting from the "Preparing the application for use" part? Sorry, this was my first time flashing a rom and I still don't know much.

Should the phone be off during the process or on? And does it put the phone into a factory reset state after it updates?

EDIT: The phone is rooted again, with superuser, but it seems to not work, and now the computer no longer recognizes the phone when it becomes connected. I cannot get a superuser request when using "su" in terminal emulator and cannot verify root with root check anymore. This is strange, because just a few minutes ago, when I had just finished re-rooting, everything was working fine.

Last edited by androidwkim; September 5th, 2012 at 09:40 PM. Reason: New issues

androidwkim

Sorry for double-posting, but i thought it would be awkward to make yet another edit. I simply re-rooted and re-installed the recovery software, and now I have the rom flashed.

I reflashed your rom, and am now on v20b, but the installer still crashes every time I start it up. I'm not sure what's going on.

I've tried re-downloading and re-flashing your rom, but the apps installer continues to crash.

I have a Telus Shine Plus, if that makes a difference.

karendar

Hi,

I'm actually doing a phone upgrade right now to test it out. Don't know why installer would crash like that on start up... Have you tried a factory reset through recovery?

darkelf76

I just wanted to add my 2 cents.. Finally decided to play with my shine now that v20b arrived and the phone stopped sucking.
I updated via the LG software without a problem, installed the clockwork recovery (though it's not recognized by the ROM manger app)
I had a full ROM and app back-ups ready to go, wiped clean and then installed the R4 without a problem, but once I went into the android market and started to get titanium to re-install all my apps, any attempt for the market to install an app rebooted the device.
As soon as I restored everything returned to normal, but I haven't gotten to enjoy this ROM yet as a result

androidwkim

Ok, so there seems to be a problem that occurs after the flashing process that causes the apps installer to crash.

I flashed the rom and then re-cleared the cache and davlik cache without reflashing the rom, and now everything is working properly.

The major issue I have is that the battery is not calibrated, I think staying on a messed up 2.3.3 for a few months messed up the phone. The battery drains very quickly, fluctuates up and down, and when it finally dies at "0", I can restart the phone and I will be able to use it for another 10 minutes before it dies again.

It seems like the phone is reading the battery percentages incorrectly? I had this problem on my jailbroken iPod Touch 4G as well, but I've come to the conclusion that it's a rare problem after trying to dig through the internet for info.

karendar

Some android phones have issues with their fuel gauge chip. This phone is one of them, sadly... Only way I've found to circumvent this is to charge the battery with an external charger. Considering I own three of these devices now, I have some experience with the issue. But I've come to consider this as an Android thing, considering my Galaxy S2 does the same thing.

karendar

The ROM does in fact seem to have market issues. I'm thinking it's due to the fact that the old ROM works with the old Android market and the new one works with Play Market. It seems to cause some confusion with the data, which messes up the market. I'll try and implement a fix for it in the next release, I just don't know when I'll have time, sadly. The fix would be this: Update ROM to latest Play Market and add a script to delete market data when flashing (Mount data partition, delete the right data folder, unmount)

androidwkim

After flashing, I simply cleared cache and davlik cache and everything works fine now. Is this a safe solution?

androidwkim

Hmm, this is actually my sister's phone, and I simply did everything for her because she doesn't know that much about technology. She always charges with her wall charger, and her battery life is still really bad. Is there any fix for this? My iPod had a similar problem and no one could help me fix it.
Thanks again,

karendar

Yes, it's a safe solution. No worries there! The only thing I would have done more is go in Settings, Applications, All apps, find Play Store or Android Market (Or market) and clear data...

As for the battery issue, there isn't much you can do other than replace the battery, I'm afraid... Someone has posted on the main forum a seller on ebay that supplies batteries for this phone. I've ordered one, as it apparently gives pretty good battery life! I do know my custom ROM seems to be nicer on the battery side because of a few tweaks compiled into it also... Otherwise, I'm limited on what I can offer to help.

androidwkim

Ok, thanks for all of the help, this is an awesome rom and this phone feels better than new. Do you have an estimate of when R5 might come out?

karendar

No ETA's as of yet, I don't have much time to work on it... And most of what I'll do is cosmetic fixes if I do release R5, haven't done any kernel work.

**EDIT** Found a workaround for auto brightness until I can figure out why the liblights are broken, but enabling it breaks brightness control. I'll supply it as a secondary patch to add to the ROM. And also managed to implement ICS transition animation inside the ROM... I think I'll integrate it in the next release.

Last edited by karendar; September 12th, 2012 at 03:12 PM.

androidwkim

Great, thanks for all your hard work!

karendar

Found a way to disable fast dormancy in our ROM. Fast Dormancy is a feature that's not activated on most carriers and has a tendency to drain battery when the carrier doesn't support it. I'll post a guide later this week to get Fast Dormancy deactivated. It really stops the phone from doing alot of wake states which drains battery needlessly.

Hopefully it'll help... If not, eh. Was worth a shot.

androidwkim

I have another question, would running the V6 supercharger script have any noticeable effect on the rom?

karendar

The kernel doesn't support everything in V6 supercharger and I cannot confirm or warrant that it'll work, so trying is at your own risk and perils. I wouldn't see why it'd be an issue though! If it doesn't work, just boot into recovery (Vol down + home + Power) and flash ROM back or factory reset (Or restore the CWM backup you did, which I recommend most)

androidwkim

There seems to be another bug, when I reboot the phone or turn it back on after draining the battery, I keep on getting "process ****** has stopped" messages, which only goes away after I clear the cache and davlik cache. It usually gives me a lot of notifications involving random apps like gallery and phone, but those only appear once. However, I keep on getting the messages for the android process. The messages render the phone unusable because they pop up within one second of being closed. Is this something wrong with my phone or the ROM?

EDIT: Lol I didn't realize that I put "won't go away" before. It goes away after clearing the two caches.

Last edited by androidwkim; September 29th, 2012 at 04:53 PM.

cjmaniac

Mine does this once in a while too. I only need to clear dalvik cache and reboot again and it works fine.

karendar

Do you guys use app2sd by any chance? Because there seems to be a problem with dalvik symlinking when you do. If you don't, no idea why it does that...

I really don't have much time to mess around with R5 to be honest, but I'll see what I can do.

Android Bob

Hi Karendar, I leave the forum for three months only to return and find that you and Jparasite have been very busy boys creating the new and improved LG Shine Plus. Awesome work guys. BTW, I don't know if you are aware that our beloved Shine Plus is being offered for sale at Future Shop for $79 on a Telus Pay as you Go plan, most likely due to the new life that you guys have brought to this phone.

How do I go about giving your R4 ROM a try? Is the Clockwork Recovery and ROOTING now incorporated into the R4 ROM, and do you still have Nuance Voice Control which is still very important to me?

I am running Android version 2.3.3 Kernel version 2.6.35.7-perf+ vinod.ramani@si-rd10-BLD168#1 GRI40 Software version LG-C710h-V20b and Amon Recovery Ver 3.06 and Link2sd.

I am hoping that I can flash your R4 ROM still using Amon Recovery. I assume that once the R4 ROM is installed that you then can launch into Clockwork Recovery by holding the Vol-+ Home + Power buttons on the LG Shine Plus (as we did with Amon).

Looking forward to your reply and as always thanks to you in advance.

Last edited by Android Bob; October 3rd, 2012 at 02:54 PM.

cjmaniac

The Amon Recovery will still work fine to flash this Rom. You would need to Root and change the Recovery yourself if you wanted to use Clockwork prior to installing the newer rom, but I never bothered. Amon seems to work well for me. Never used Voice Control so I can't help you there.

Android Bob

Just to be sure that I fully understand and follow what you are saying (please be patient with me) as I am new to this Custom ROM scene all I have to do is as follows:

(1) I am rooted (Ginger break 2.3.3) running stock Android 2.3.3 v20b
(2) Performed a Nandroid Backup using Amon Recovery v3.0.6
(3) Performed a Full Backup using Titanium Backup Pro
(4) Download Karendar's R4 Zip file from Page 1 of this thread, unzip (on my PC) and install the files to the / directory of my SD Card and Flash using Amon Recovery
(5) Result new R4 Custom ROM should be installed with Clockwork Recovery and no further rooting required

If I am wrong in any of my steps, please set me on the right path.

Looking forward to your reply and as always thanks to you in advance.

cjmaniac

You do not unzip the file. Just copy it to SD card and flash the zip file.

Clockwork recovery is a seperate install process. I believe there is a thread on how to install it but I am not too sure.

karendar

I've been meaning to write a whole new tutorial step by step to get the phone rooted + clockworkmod + Custom ROM... Because info is pretty spread out right now. But yeah, copy zip to SD card, flash with Amon RA, rince, recycle, repeat.

Just keep in mind that Link2SD will probably be broken after flashing custom ROM... Might have to be reinstalled. I currently use app2sd instead of link2sd, faster and less of a hassle... But it's not beginner friendly sadly.

I hardly have any time for the forum as of late... It's pretty dead anyways! hehe.

As for the Future Shop 79$ deal, yeah... I bought one for my mom and it had v20a on it. I flashed v20b on it so quickly I didn't even boot it for more than 2 minutes on v20a!

And for Nuance, yes they fixed it (Tested english and french, works for me) and it is in my ROM too...

androidwkim

This is very strange, but I seem to have forgotten how to get into recovery. Lol I spent time on other devices and forgot. Is the button combo volume-down and power? It doesn't seem to work anymore. I've tried the reboot recovery option from the power menu, and reboot recovery with su in terminal emulator. Nothing seems to work. How could a recovery disappear like that?