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

Root CyanogenMod 7 Unofficial Beta 5 02/20/12

wetbiker7 said:
Ok , I really don't know what I've installed that causing me problems . Last night when I was talking to a friend , I did a Titanium restore . The restore went well and the phone was running great . I went to reboot and all the apps I had restored disappeared . I rebooted and magically they reappeared . This happened several times after rebooting . I thought that Titanium may be the cause so I installed them manually the next time after a fresh install of beta 5 . Today the darn phone started doing it again . I've gotta conflict on Beta5 with the one or more of the apps I'm running , I think . I reverted back to the previous version of CM7 today and my phone is running like a champ . Same apps , same set up minus S2E on Beta5 . Gotta have my phone through the week so I'm gonna work on it some more this weekend and find out were my conflicts are . :confused:
Click to expand...

Are you saying you are running S2E on Beta 5? Why???
 
cdaleman81 said:
I guess it depends on what you need. I used to run Linux back in the day when one accessed the net through a dial-up modem, so I do have some experience dealing with ppp on Linux, but not sure it's applicable to what you're looking for...
Click to expand...

our phones uses ppp for the mobile data

my rom connects to the 3G network and gets internet just fine

when you turn on wifi, it disconnects the ppp0 interface and then the wifi interface eth0 becomes the active route

when you send an MMS when you are connected to wifi it tries to establish the ppp connection, but fails

I beleive MMS needs to go over the ppp0 mobile data interface

i think the MMS proxy will only allow connections coming from that network

i need help figuring out why the ppp connection fails when we are on wifi

when you send the MMS it should establish the ppp connection, send the mms message and then disconnect

do you know how to use logcat?
 
hroark13 said:
ill test when i get a chance tommorow and put a new one out if needed
Click to expand...


i messed up, that zip does not have a boot image for some reason

here is a link to the beta 4 kernel

beta4d_kern_cwm.zip


the only difference between the beta 4 kernel and the beta 5 kernel is integrated apps 2 sd and the smaller modules

i will be making a new kernel soon and I will be sure to make an apps2sd version and on non apps2sd version to give people a choice
 
hroark13 said:
i messed up, that zip does not have a boot image for some reason

here is a link to the beta 4 kernel

beta4d_kern_cwm.zip


the only difference between the beta 4 kernel and the beta 5 kernel is integrated apps 2 sd and the smaller modules

i will be making a new kernel soon and I will be sure to make an apps2sd version and on non apps2sd version to give people a choice
Click to expand...


i re-made that zip for you

Prevail_cmbeta5_no_ext_BOOT_cwm.zip

let me know how it works
 
hroark13 said:
our phones uses ppp for the mobile data

my rom connects to the 3G network and gets internet just fine

when you turn on wifi, it disconnects the ppp0 interface and then the wifi interface eth0 becomes the active route

when you send an MMS when you are connected to wifi it tries to establish the ppp connection, but fails

I beleive MMS needs to go over the ppp0 mobile data interface

i think the MMS proxy will only allow connections coming from that network

i need help figuring out why the ppp connection fails when we are on wifi

when you send the MMS it should establish the ppp connection, send the mms message and then disconnect

do you know how to use logcat?
Click to expand...

I follow you. Hmmm... yes, no reason both interfaces can't exist simultaneously that I can think of. I haven't used logcat, but interested in learning.
 
I have had a weird problem occur with Beta 5 three times.

This never happened when I was running hroark's original solution kernel with the Previous Beta.

The first time this happened I was still on my old SD card and I joked that I had had an Acid Flashback. No more jokes about this. It has happened twice more.

Basically, I reboot the phone and it acts as though a factory reset has been done, except that I have found that data is still on sd-ext.

I assume somehow the symlinks get destroyed and the system boots with the empty data partition. Sd-ext is still loaded with apps but system ignores them and uses old data partition to rebuild Dalvik for system apps only since no user apps are seen. I don't know if anything on sd-ext is corrupted.

This third time I had a very recent CWM backup. so I flashed the Beta 5 zip and restored the backup and everything was back like before.

Before I did that I played around with it a little. I just flashed the Beta 5 zip without a factory reset. The apps were still on sd-ext but I started having problems.

I actually lost all connectivity, but it is possible that I deleted something out of the system folder by mistake but highly unlikely. I tried flashing the Beta 5 kernel but that did not help.

I finally restored an old backup before beta 5 and connectivity.came back.

Then I factory reset, flashed Beta 5 and restored the newest backup. Everything good now.

What could be causing this situation where it ignores sd-ext and does a half ass reset using the old data partition to rebuild Dalvik for the system apps?

I blame Kouma. I don't know why, but he looks guilty.
 
I was kidding about Kouma of course, but I said that because of this:

This never happened with the original sd-ext kernel using the prior Beta

Kouma was talking about making it slick enough to revert to using the original data partition if it did not find an SD card or a valid sd-ext.

What would cause this to be triggered in error, I do not know, possibly a timing issue with SD mounting?

It has happened to me with two SD cards. Both 16GB with 1GB sd-ext

Once on the old one and twice on the new one.
 
Then I'm not having an app conflict or card problem . It's something else . Thanks , that will save me some time . I was gonna reinstall beta5 this weekend and run a trial and error with each app . Glad I don't need to do that now . :D I thought it may be Titanium but I installed all the apps without and still had the same issue .
I wonder what's causing it , hroark ?
 
wetbiker7 said:
Then I'm not having an app conflict or card problem . It's something else . Thanks , that will save me some time . I was gonna reinstall beta5 this weekend and run a trial and error with each app . Glad I don't need to do that now . :D I thought it may be Titanium but I installed all the apps without and still had the same issue .
I wonder what's causing it , hroark ?
Click to expand...

Mine is running great now. I don't know shit from shinola but I suspect a minor tweak in the kernel is causing this.

After the second time, I suspected it had to do with changing batteries so I did not for 2 days.

I was going to test out that theory and it did it the third time before I had the chance. Lol.

I have rebooted the phone off the charger many times, but I do not remember if it was on the charger when this happened last night.

I know when you shut the phone down, the last thing I see is a quick message saying that the SD is safe to remove.
 
yeah monster..its deff a cm7 thing...soft keys work on Ct and stock...i did notice you can make the four soft keys vibrate on a long press... but thats it
 
wyelkins said:
I have had a weird problem occur with Beta 5 three times.

This never happened when I was running hroark's original solution kernel with the Previous Beta.

The first time this happened I was still on my old SD card and I joked that I had had an Acid Flashback. No more jokes about this. It has happened twice more.

Basically, I reboot the phone and it acts as though a factory reset has been done, except that I have found that data is still on sd-ext.

I assume somehow the symlinks get destroyed and the system boots with the empty data partition. Sd-ext is still loaded with apps but system ignores them and uses old data partition to rebuild Dalvik for system apps only since no user apps are seen. I don't know if anything on sd-ext is corrupted.

This third time I had a very recent CWM backup. so I flashed the Beta 5 zip and restored the backup and everything was back like before.

Before I did that I played around with it a little. I just flashed the Beta 5 zip without a factory reset. The apps were still on sd-ext but I started having problems.

I actually lost all connectivity, but it is possible that I deleted something out of the system folder by mistake but highly unlikely. I tried flashing the Beta 5 kernel but that did not help.

I finally restored an old backup before beta 5 and connectivity.came back.

Then I factory reset, flashed Beta 5 and restored the newest backup. Everything good now.

What could be causing this situation where it ignores sd-ext and does a half ass reset using the old data partition to rebuild Dalvik for the system apps?

I blame Kouma. I don't know why, but he looks guilty.
Click to expand...


try flashing the original MOD I made from that thread

I addded 2 mount lines for data in Beta 5 trying to follow Kouma's example so that the /data would mount if there was not sd-ext

my original mod only had the one mount line

try it and let me know if the problem persisits
 
VWill do Hroark. I feel confident that will fix that problem. But what else did you add to the Beta 5 kernel that I wont have?

I can't figure out what glitch triggers it to happen. I used CWM to format the new SD in its entirety when I first got it. And then, of course, used it to format sd-ext. Which also happens if I do a wipe.

But it never happened with the original kernel.

Not really even a big deal if I backup often enough now that I understand what is happening.

I'll flash the old kernel now.

I assume you mean:

cm7d2x.zip

EDIT: so far so good.
 
My guess, and that is all it is, but I would think what is triggering it is the sd card is not mounting fast enough and so the kernel mounts to the next location.
 
new optimus said:
My guess, and that is all it is, but I would think what is triggering it is the sd card is not mounting fast enough and so the kernel mounts to the next location.
Click to expand...

Yep, that was my thoughts too, but not sure why so intermittent. I reboot and turn phone off all the time.
 
new optimus said:
I only have vague half formed guesses as to why its intermittent. nothing I would even put into words.
Click to expand...

And since hroark modified his code to match Koumas from the CTMOD kernel, to try to prevent a non boot the question becomes, has anyone seen this problem occur on that kernel and ROM. Same phone. Bigger test group possibly at the moment.
 
I flashed the new beta and everything was working fast but when I did the mod for the sd card my phone has been force closing facebook and a few other apps and it has been working a lot slower. Im thinking about reflashing the new beta and leaving it alone. Everything else ok.
 
BiLlYsIlNeS said:
I flashed the new beta and everything was working fast but when I did the mod for the sd card my phone has been force closing facebook and a few other apps and it has been working a lot slower. Im thinking about reflashing the new beta and leaving it alone. Everything else ok.
Click to expand...

try to fix permissions first... that is known to fix *some* fc issues
 
BiLlYsIlNeS said:
I flashed the new beta and everything was working fast but when I did the mod for the sd card my phone has been force closing facebook and a few other apps and it has been working a lot slower. Im thinking about reflashing the new beta and leaving it alone. Everything else ok.
Click to expand...

I think Hroark already included a Sdtweek in the init.d folder...Maybe that might be causing your issues
 
Perhaps someone can shed some light on this for me:

Somehow my maps.apk got updated and died. After killing processes and cache I uninstalled maps with TB. I then proceeded to reinstall from the zip provided on page 1 using CWM. I reboot and run maps and it gets as far as zoning in on my area and then it freezes. If I touch anything it takes a sec then asks to wait or FC. I have attempted to install the apk provided in the zip by means of CWM, ADB PUSH and just plain copy paste reboot method with Root explorer all yielding the same turnout.

With every method of install I immediately checked the version number of maps.apk and it comes up 6.0.3 every time and that sounds wrong. I may be losing it in my old age but I could have sworn the stable apk was version 5 something. I also tried pulling maps from the removed apps zip on the same page as googlemaps zip, both get the same results.

Any insight to this issue would be most appreciated.
----------------------------------------------------------------------------
I remembered I still had the beta 3 install package so I took that version of Maps and used adb push to install. After a quick reboot all is well. The version of maps that worked is 5.8.0
 
You must log in or register to reply here.
Back
Top Bottom