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

Root [Rom][5-17-12]Broken Out Connect 1.0 w/ Blitzkrieg Kernel

brian1981 said:
I followed all the steps and it completed successfully but when I rebooted the Lucid it started looping. Now all it does is constantly reboot. Idea???
Click to expand...

I'm curious since you are not the first lucid user to try and flash this. (which is made for the connect) Is somebody somewhere saying it's ok and have done successfully?

Anyway if you made a backup you could try restoring it.
 
jimbojimshorts said:
first off i want to theank you. i messed my esteem up by rooting, roming, and forgeting to back up. i didnt like the rom i put in and did a factory reset. lol yeah i know. dumb. anyways your blitzkrieg rom is the only thing i could get to work that saved my phone. so thank you so much. now....i want to take it up to metro and get it turned back on. do i need the metro pcs firm ware in it to do that? where might i find that? also how can i put a basic lg key board into it? all that is in there is swype and i really dont care for it. thanks again for your help
Click to expand...

Do you have the esteem or the connect? If you want to restore everything to stock you can use the lg update tool. I believe this method also works for the esteem.
 
Hey pg, found something a little bit strange in the logs. Seems to be an error being reported by the kernel over and over. Looks to be related to cpufreq, since it keeps looping i bet it's chewing up cpu quite a bit. :

Code: 
[  724.288259] ------------[ cut here ]------------
[  724.288279] WARNING: at fs/sysfs/group.c:138 sysfs_remove_group+0x58/0x114()
[  724.288288] sysfs group c0975ca8 not found for kobject 'cpufreq'
[  724.288295] Modules linked in: wireless [last unloaded: wireless]
[  724.288307] Backtrace: 
[  724.288331] [<c0105a98>] (dump_backtrace+0x0/0x110) from [<c066713c>] (dump_stack+0x18/0x1c)
[  724.288340]  r7:00000009 r6:0000008a r5:c02a54c4 r4:dcf77d40
[  724.288359] [<c0667124>] (dump_stack+0x0/0x1c) from [<c01b9e0c>] (warn_slowpath_common+0x54/0x6c)
[  724.288372] [<c01b9db8>] (warn_slowpath_common+0x0/0x6c) from [<c01b9ec8>] (warn_slowpath_fmt+0x38/0x40)
[  724.288381]  r9:00000001 r8:0e052000 r7:c003d698 r6:dda03500 r5:c0975ca8
[  724.288395] r4:00000000
[  724.288405] [<c01b9e90>] (warn_slowpath_fmt+0x0/0x40) from [<c02a54c4>] (sysfs_remove_group+0x58/0x114)
[  724.288414]  r3:c0975ca8 r2:c0785792
[  724.288432] [<c02a546c>] (sysfs_remove_group+0x0/0x114) from [<c04cd1b8>] (cpufreq_governor_smartass+0x2c4/0x318)
[  724.288442]  r7:c003d698 r6:00000000 r5:c0e0ae34 r4:ce08f698
[  724.288465] [<c04ccef4>] (cpufreq_governor_smartass+0x0/0x318) from [<c04c53cc>] (__cpufreq_governor+0xe4/0x130)
[  724.288482] [<c04c52e8>] (__cpufreq_governor+0x0/0x130) from [<c04c7128>] (__cpufreq_remove_dev+0x344/0x3cc)
[  724.288491]  r7:c0df5540 r6:60000013 r5:00000001 r4:d5083b60
[  724.288509] [<c04c6de4>] (__cpufreq_remove_dev+0x0/0x3cc) from [<c0666ffc>] (cpufreq_cpu_callback+0x8c/0xac)
[  724.288525] [<c0666f70>] (cpufreq_cpu_callback+0x0/0xac) from [<c01dc4a4>] (notifier_call_chain+0x34/0x78)
[  724.288534]  r7:00000000 r6:ffffffe1 r5:dcf77e9c r4:00000001
[  724.288551] [<c01dc470>] (notifier_call_chain+0x0/0x78) from [<c01dc598>] (__raw_notifier_call_chain+0x1c/0x24)
[  724.288566] [<c01dc57c>] (__raw_notifier_call_chain+0x0/0x24) from [<c01bc048>] (__cpu_notify+0x30/0x4c)
[  724.288584] [<c01bc018>] (__cpu_notify+0x0/0x4c) from [<c0657098>] (_cpu_down+0xb4/0x2cc)
[  724.288597] [<c0656fe4>] (_cpu_down+0x0/0x2cc) from [<c06572e0>] (cpu_down+0x30/0x44)
[  724.288611] [<c06572b0>] (cpu_down+0x0/0x44) from [<c06578e4>] (store_online+0x3c/0x80)
[  724.288619]  r5:0000001e r4:ce08e008
[  724.288633] [<c06578a8>] (store_online+0x0/0x80) from [<c03d43b8>] (sysdev_store+0x24/0x28)
[  724.288641]  r5:dcf77f70 r4:ddb11db0
[  724.288660] [<c03d4394>] (sysdev_store+0x0/0x28) from [<c02a2448>] (sysfs_write_file+0x110/0x144)
[  724.288677] [<c02a2338>] (sysfs_write_file+0x0/0x144) from [<c024d310>] (vfs_write+0xb8/0x164)
[  724.288690] [<c024d258>] (vfs_write+0x0/0x164) from [<c024d480>] (sys_write+0x44/0x70)
[  724.288699]  r8:0000001e r7:00000000 r6:00000000 r5:4010ce3c r4:dcd01f40
[  724.288719] [<c024d43c>] (sys_write+0x0/0x70) from [<c0101440>] (ret_fast_syscall+0x0/0x30)
[  724.288727]  r8:c01015e8 r7:00000004 r6:0000000b r5:4010ce3c r4:0000b10c
[  724.288742] ---[ end trace 95144ad58db7e446 ]---
 
Spec2nirvash said:
Can anybody tell me why TTS, (default pico or any other engine) will not work with this ROM? Second time flashing and can't get it to work!
Click to expand...

The PicoTts.apk is missing from the system folder. I deodexed it and have in system > app. It appears as an option in Settings, but cannot get it to work apparently. D=
 
Installed this ROM today and had no issues at all all, at least no major ones.

Just one that bothered me a litle bit was trying use SetCPU for scaling and it kept resetting itself back up to 1.5 ghz instead of the 1.2 I wanted to set it at.

You guys think this could be a kernel or Rom issue?
 
Vyrus69 said:
Installed this ROM today and had no issues at all all, at least no major ones.

Just one that bothered me a litle bit was trying use SetCPU for scaling and it kept resetting itself back up to 1.5 ghz instead of the 1.2 I wanted to set it at.

You guys think this could be a kernel or Rom issue?
Click to expand...

Use No frills CPU and go to settings in
N.F.CPU, make sure you check "prevent changes by other apps" .... it should make the CPU speed stick...
 
Actually NFCPU doesn't even throttle down the CPU speed, it keeps it at the max, so I tried installing the Plague kernel as well, but it keeps resetting it back to the max.

So this is a ROM issue it seems, so I'm off BO because I don't liker overclocking and stressing the processor personally.

So the quest continues.
 
You need to find the reg version of no frills ... it'll throttle up or down and yes it sticks. When B.O.R. inititially released that's what came with it...some ppl had problems with it sticking until they found the "prevent changes" in the settings.
I've used B.O. & Plague this way since they both released as many others have.
 
Vyrus69 said:
Actually NFCPU doesn't even throttle down the CPU speed, it keeps it at the max, so I tried installing the Plague kernel as well, but it keeps resetting it back to the max.

So this is a ROM issue it seems, so I'm off BO because I don't liker overclocking and stressing the processor personally.

So the quest continues.
Click to expand...

If you go back and read this thread from the beginning you'll see what I'm saying
 
Vyrus69 said:
Installed this ROM today and had no issues at all all, at least no major ones.

Just one that bothered me a litle bit was trying use SetCPU for scaling and it kept resetting itself back up to 1.5 ghz instead of the 1.2 I wanted to set it at.

You guys think this could be a kernel or Rom issue?
Click to expand...

This issue has already been addressed many times. The culprit for the CPU not sticking after each boot is the /etc/init.qcom.post_boot.sh file. You have to add these lines:

Code: 
	 echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
	 echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
	 echo 1242000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
	 echo 1242000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

Right below this line:

Code: 
	 chown system /sys/devices/system/cpu/cpu1/cpufreq/ondemand/sampling_rate

You can also change the min_frequency and max_frequency [in Kilohertz] to the speed you want your CPU to run. So if you have 192000KHz, the speed really is 192MHz. For 1242000KHz = 1242MHz

Also, you want to comment out these lines in the file by adding a # at the beginning:

Code: 
        start mpdecision

and

Code: 
        start thermald

at the bottom of the .sh file, so they look like this:

Code: 
        #start mpdecision

and

Code: 
        #start thermald

The original thread discussing this solution is here.

---------------------------------------------------------------

Spec2nirvash said:
I fixed it. Had to find PicoTTS.apk and TtsService.apk online. I downloaded, then installed through root explorer. I finally have my Ivona back :D
Click to expand...

I worked all morning on a flashable zip [I am going to call them Flashies from now on. :p] and the problem is now 100% fixed. It should work just fine for Broken Out and for Black Plague. The thread having all the instructions & the Flashie is here. :)
 
Could anybody help me. everytime i try and install the zip file from sd card and reboot after instillation my phone goes into a bootloop mode . any help woukd be greatly appreciated.
 
Is it alright to put the LG Stock Lock screen back on this ROM?

Thanks man for the work on this ROM! I will try it out one day and when I get a job I am going to donate to everyone that has made ROMS and has helped me out (you know who you are).... :)


Oh yea, one more thing... sorry, is there a ROM that will increase the in call volume? Not the loud speaker (I have Volume+ installed but it just does the speakerphone part) my LG is the quietest phone I have ever had!
 
airtioteclint said:
You downloaded the delooper i posted 3 posts up right?
This one. http://www.shabbypenguin.com/OUDstuff/cayman/CWM-Loop-DeLooper.zip
Click to expand...


Hi, is that de looper for the LG Connect? I had this problem last night....

"Well last night I fried "Version Two" ROM I was playing with the boot animations in ROM Toolbox and I changed the boot animation and when I restarted the boot animation just kept looping over and over and over so I went to Clockwork and put on Black Plaque to try it out and I must say that I like it 10x better than version 2! So far so good!I have not had any ghost reboots YET.... But on the app "Pimp My Rom" what settings do I change to smooth out the scrolling, etc.... It doesn't come with any instructions nor does it tell me what each thing does. I also keep getting an error from Pimp my Rom about every few hours, it says this "Sorry! The application PIMP My RoM (process com.androguide.pimp.my.rom) has stopped unexpectedly. Please try again. Then I have the option to Force Close or Report and I have reported it about 5 times now.... Grrrr"
 
zandersig said:
Hi, is that de looper for the LG Connect? I had this problem last night....

"Well last night I fried "Version Two" ROM I was playing with the boot animations in ROM Toolbox and I changed the boot animation and when I restarted the boot animation just kept looping over and over and over so I went to Clockwork and put on Black Plaque to try it out and I must say that I like it 10x better than version 2! So far so good!I have not had any ghost reboots YET.... But on the app "Pimp My Rom" what settings do I change to smooth out the scrolling, etc.... It doesn't come with any instructions nor does it tell me what each thing does. I also keep getting an error from Pimp my Rom about every few hours, it says this "Sorry! The application PIMP My RoM (process com.androguide.pimp.my.rom) has stopped unexpectedly. Please try again. Then I have the option to Force Close or Report and I have reported it about 5 times now.... Grrrr"
Click to expand...

The pimp my rom app just got updated to v1.9 hopefully the dev fixed the fc issue, but if u wnt to fix the scrolling issue try changing the vm heap size inside build. prop to 48m
 
zandersig said:
Hi, is that de looper for the LG Connect? I had this problem last night....

"Well last night I fried "Version Two" ROM I was playing with the boot animations in ROM Toolbox and I changed the boot animation and when I restarted the boot animation just kept looping over and over and over so I went to Clockwork and put on Black Plaque to try it out and I must say that I like it 10x better than version 2! So far so good!I have not had any ghost reboots YET.... But on the app "Pimp My Rom" what settings do I change to smooth out the scrolling, etc.... It doesn't come with any instructions nor does it tell me what each thing does. I also keep getting an error from Pimp my Rom about every few hours, it says this "Sorry! The application PIMP My RoM (process com.androguide.pimp.my.rom) has stopped unexpectedly. Please try again. Then I have the option to Force Close or Report and I have reported it about 5 times now.... Grrrr"
Click to expand...
The delooper won't help you with that problem if I remember correctly. I believe that it's used when your phone keeps booting into CWM recovery. It should remove CWM recovery &give you the stock factory recovery back.
 
zandersig said:
Where do i locate the vm heap in pimp my rom?
Click to expand...

PmR v2.0 has just been pushed to the market but may take some time for them to make it available but you can always go to the actual thread using the link in my post. The new update will include the option to change the vm heap size and much much more... :D
 
Installed on my handset first day out the box......everything cool......how ever when i multi task my handset tend to reboot.....can anybody explain that????
 
Shatterproof said:
The pimp my rom app just got updated to v1.9 hopefully the dev fixed the fc issue, but if u wnt to fix the scrolling issue try changing the vm heap size inside build. prop to 48m
Click to expand...


Where is this located at in the app? I can't find it.

"vm heap size inside build. prop to 48m"

Thanks!
 
zandersig said:
Where is this located at in the app? I can't find it.

&quot;vm heap size inside build. prop to 48m&quot;

Thanks!
Click to expand...


The new update to pimp my rom should have that adjustment if not u can use either rom toolbox or root explorer. If u use root explorer u got to go to system folder then scroll to where the build.prop is open it with text editer (by long pressing on the file a menu will pop up with that choice in the menu) then scroll down to where it says vm heep and change it to 98 or 128 (i think is the highest it says it'll go in rom toolbox to b safe but dont quote me on that) then save it and reboot and it should b changed. Also when u save the build.prop with ur changes through root explorer it will automaticaly back up the original
 
Yea I looked all through Pimp my Rom app and there is no spot to type any numbers in anywhere. I will try ROM Toolbox.
 
You must log in or register to reply here.
Back
Top Bottom