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

Root [ROM] Jiilik's custom Shine Plus ROM's

I'll give it try tonight. I've never used Option 22, LOL that's probably my problem. I am using 4.9 APK. If I can get that to work, then I'll work on the power menu.

I'll keep in mind your notes, since they do involve modifying XML files and adding new PNGs. Hopefully once I get that Power Menu working, I'll merge it with your changes as well.

By chance, could you also explain how you managed to do the update.zip for your CRT mod? (The only thing I know how to do is use the kitchen to make a fully featured ROM to flash).
 
jparasite said:
I'll give it try tonight. I've never used Option 22, LOL that's probably my problem. I am using 4.9 APK. If I can get that to work, then I'll work on the power menu.

I'll keep in mind your notes, since they do involve modifying XML files and adding new PNGs. Hopefully once I get that Power Menu working, I'll merge it with your changes as well.

By chance, could you also explain how you managed to do the update.zip for your CRT mod? (The only thing I know how to do is use the kitchen to make a fully featured ROM to flash).
Click to expand...

There are tons of guides for edify scripts (updater-script)... But here's a link:
How to Create Android Update Zip Package | All About Web & Mobile Application Development

Otherwise, an easier way would be to just grab the zip file, delete the files from system out of the zip and then add your own. The script copies everything from the system folder to the phone... ;)
 
I have an idea that may fix the 3D apps crashing issue when the cpu is overclocked.

I was playing+testing a game called "Apparatus"(so much fun) which I can change the graphics settings and draw fps.
The game did not crash at higher graphics settings, but when trying to lower them for smoother gameplay, it crashed after some time.

So my assumption is that the GPU only crashes when the fps exceeds a certain limit, while at lower clock rates or when playing demanding games in higher clock rates, that certain limit cannot be reached, so that explains why the GPU won't crash.

Then I did some unscientific testings.
Since the game has an option to draw fps, I could identify the fps when it crashes.

Turns out the crashes only occur when fps is higher than 50 for some time(not necessarily continuous). it tends to crash at above 45fps but will never crash as long as the fps don't hit above 50.
I didn't have the patience to do a detailed experiment cause every time it crashes, I need to reboot in order to perform another test...it's quite annoying.

So maybe we can cap the fps ,say at 40 or 45...I googled it, but couldn't find how, need to modify the kernel?

just my thoughts, maybe it sounds stupid to you experts haha:D
 
fps is a result, not something controlled by the kernel or program. if it needs to do more for rendering, the resulting fps is lower.
 
Well ever since Jiilik added AVS (Adaptive voltage scaling) to his kernel, I managed to get a 768 mhz overclock stable with most games... The CPU/GPU combo isn't reputable as the most stable when overclocked though.
 
So I've managed to successfully mod the Power Menu to include Reboot/Recovery. Expect it posted later today once I've put it into flashable package form and tested it a few times.

I'm now looking at adding in a Rotary unlock, but god damn working in Dalvik assembly is a nightmare. I really wish LG's sources would compile properly.
 
Hey jiilik, do you know if the kernel we're running on is .32 or .35? I'm thinking of looking into the LG P500h kernel sources and seeing if we can port some of franciscofranco's changes to this one.
 
jparasite said:
Hey jiilik, do you know if the kernel we're running on is .32 or .35? I'm thinking of looking into the LG P500h kernel sources and seeing if we can port some of franciscofranco's changes to this one.
Click to expand...

It's 2.6.35.7, with sources from codeaurora patched by LG. My main patches are for overclocking (sources were posted in the OC thread). Other than that, any of my changes are in the build options, which you can access using 'make menuconfig' after the initial configuration is loaded.

Cheers
 
so my wife ran your 001 for a while but had that dalvik issue alot (making phone useless). so I just updated her to 008 which hasn't exhibited the dalvik issue but has started an issue almost daily with the screen going black, phone locking up like that with red led showing, and it eats battery the whole time. have to pull battery and restart to get it to work again.

this is also making the phone almost useless to her for reliability.

I appreciate all the incredible work going into this, but the black screen issue, if this is what she's experiencing, is extremely prevalent and very serious. any ideas yet on this? can we help test experimental builds or something to see if it helps considering this happens pretty much daily?

any idea how to prevent it from happening?

her phone has 008, the cool blue theme mod, and is running stock otherwise. only has a couple of apps installed (facebook, titanium backup, using stock speeds (haven't even installed setcpu yet because it's already much faster than it ever was before), a flashlight app for the flash led, and the over media console library book management thing which she uses to read her online books with every night.

Thanks for the hard work so far - if there's any way I can help solve this one serious remaining (new?) issue then let me know please.

Don
 
dkelley said:
so my wife ran your 001 for a while but had that dalvik issue alot (making phone useless). so I just updated her to 008 which hasn't exhibited the dalvik issue but has started an issue almost daily with the screen going black, phone locking up like that with red led showing, and it eats battery the whole time. have to pull battery and restart to get it to work again.

this is also making the phone almost useless to her for reliability.

I appreciate all the incredible work going into this, but the black screen issue, if this is what she's experiencing, is extremely prevalent and very serious. any ideas yet on this? can we help test experimental builds or something to see if it helps considering this happens pretty much daily?

any idea how to prevent it from happening?

her phone has 008, the cool blue theme mod, and is running stock otherwise. only has a couple of apps installed (facebook, titanium backup, using stock speeds (haven't even installed setcpu yet because it's already much faster than it ever was before), a flashlight app for the flash led, and the over media console library book management thing which she uses to read her online books with every night.

Thanks for the hard work so far - if there's any way I can help solve this one serious remaining (new?) issue then let me know please.

Don
Click to expand...

If you can sideload this app: [APP] BetterBatteryStats adds battery history back to Gingerbread - xda-developers

The important part of the app is: Partial Wakelocks (since unplugged/last charge).

This will show a list of processes that are still running even with the display off and preventing the CPU from going into low power mode.

If you install my mod, you'll also be able to take a screenshot of this as well. If you can post one up, I'll better be able to help you determine what is eating up the battery life.
 
Still can't figure out why this ROM gives me a dalvik error on reboot (All android processes crash). I used a workaround (Script manager + Clear dalvik + reboot on desktop) but this isn't really a decent one... Any ideas?

I'll try and rebuild a ROM in the next few days to see if I can fix the corrupted Dalvik issue.
 
Im not 100% sure on the issue but I do have the same problem. Im trying to re-create the error but I dont see to be able to. Im thinking it may be the kernal but Im not sure if the error was present in earlier versions of the ROM
 
damien1114 said:
Im not 100% sure on the issue but I do have the same problem. Im trying to re-create the error but I dont see to be able to. Im thinking it may be the kernal but Im not sure if the error was present in earlier versions of the ROM
Click to expand...

The issue always happens when I reboot the phone. All apps start crashing... I use App2SD though, so it might be part of the issue. My workaround is to rebuild dalvik and reboot phone. As soon as I have a few minutes to do so (As in have the phone back from my girlfriend), I'll try testing to see which app causes said issue.
 
I don't use App2SD and it always does it to me. I do the same thing having to rebuild my dalvik cache. I havent been able to recreate the error with any customs roms I have made
 
damien1114 said:
I don't use App2SD and it always does it to me. I do the same thing having to rebuild my dalvik cache. I havent been able to recreate the error with any customs roms I have made
Click to expand...

I'll try and rebuild a new ROM today using my mods and add Jiilik's kernel. Flash it on the phone and see if it fixes it... Must be a corrupted APK somewhere that didn't deodex properly.

Guys, I also need your help. I really wanna fix this wifi issue and considering I'm not tech savvy on coding, I need to know what wifi chipset our phone uses. Does someone here have this info?

Thanks!
 
karendar said:
I'll try and rebuild a new ROM today using my mods and add Jiilik's kernel. Flash it on the phone and see if it fixes it... Must be a corrupted APK somewhere that didn't deodex properly.

Guys, I also need your help. I really wanna fix this wifi issue and considering I'm not tech savvy on coding, I need to know what wifi chipset our phone uses. Does someone here have this info?

Thanks!
Click to expand...

it use wifi/bt module

wifi.jpg

wifi2.jpg
 
alfi said:
it use wifi/bt module
Click to expand...

I just did a diff between v20a of our ROM and P500 V20G which is a very close brother. If I take a look at most files linked to wifi, wireless.ko is one of the rare files which has a different hex structure. All other files are almost identical... I'm gonna try and bundle a wifi fix by stealing files from the P500's 2.3.3 structure considering they're using the same chipset for BT and wifi... Maybe we can get a fix going.

Libbluetooth.so is identical in both ROMs, libbluetoothd is almost identical save a few things.

liba2dp.so is identical (Related to BT)

lgqcomm_omx.so almost identical (wifi related)

I'll package something tonight. Also, found a shine plus for dirt cheap, will try and buy it so I can leave the girlfriend's phone functional and work on another one.
 
karendar said:
I just did a diff between v20a of our ROM and P500 V20G which is a very close brother. If I take a look at most files linked to wifi, wireless.ko is one of the rare files which has a different hex structure. All other files are almost identical... I'm gonna try and bundle a wifi fix by stealing files from the P500's 2.3.3 structure considering they're using the same chipset for BT and wifi... Maybe we can get a fix going.

Libbluetooth.so is identical in both ROMs, libbluetoothd is almost identical save a few things.

liba2dp.so is identical (Related to BT)

lgqcomm_omx.so almost identical (wifi related)

I'll package something tonight. Also, found a shine plus for dirt cheap, will try and buy it so I can leave the girlfriend's phone functional and work on another one.
Click to expand...

hi karendar

my son have a lg optimus one (p500h),from koodo pretty close to mine and he upgrade to v20a 1 month ago and he never have this problem .
 
alfi said:
hi karendar

my son have a lg optimus one (p500h),from koodo pretty close to mine and he upgrade to v20a 1 month ago and he never have this problem .
Click to expand...

So I've read, the P500 has a bunch of other issues though... Wifi isn't one of them. ;)
 
Fixed my dalvik crashes on reboot. It was too stupid to be honest... The reason I was getting the FC's was because I had dalvik on data/dalvik-cache and my app folder was symlinked to SD card. Because of the fact one partition was on the SD and the other was in NAND, the phone freaked. I moved Dalvik over to the SD and everything's perfect now. Go figure...

Will test out my theory for Wifi in a minute.

**edit** Well that was a fail on my part. :P hahaha. Does not work... Errors out the wifi when I change wireless.ko. Will try it with v20a of the P500 ROM...
 
karendar said:
Fixed my dalvik crashes on reboot. It was too stupid to be honest... The reason I was getting the FC's was because I had dalvik on data/dalvik-cache and my app folder was symlinked to SD card. Because of the fact one partition was on the SD and the other was in NAND, the phone freaked. I moved Dalvik over to the SD and everything's perfect now. Go figure...

Will test out my theory for Wifi in a minute.

**edit** Well that was a fail on my part. :P hahaha. Does not work... Errors out the wifi when I change wireless.ko. Will try it with v20a of the P500 ROM...
Click to expand...
I am also experiencing the FC's but could you be clearer as To what is required to fix the problem. I don't follow what has to be copied to SD card.

Thanks
 
Android Bob said:
I am also experiencing the FC's but could you be clearer as To what is required to fix the problem. I don't follow what has to be copied to SD card.

Thanks
Click to expand...

Do you use App2SD or link2SD? (As in having an ext3 or FAT partition on your SD card for your app folder)

If you do, you have a cache called Dalvik cache which is stored in data/dalvik-cache. This cache system seems to have an issue with being on the phone while apps are on the SD card.

If not, your FC problem might be something else... What I did to troubleshoot was this:

Open a shell with adb.exe (adb shell), type SU enter
cd data/dalvik-cache
rm data@*
reboot

If your phone doesn't FC after rebooting, it means that it's your user applications that are the issue. If it still FC's, do this:

Open a shell with adb.exe (adb shell), type SU enter
cd data/dalvik-cache
rm system@*
reboot

If it doesn't FC anymore, it means something is wrong with the ROM itself (Corrupted file)
 
You must log in or register to reply here.
Back
Top Bottom