Bug Fixes and a Little More What Else Could You Ask For- Sapphire 0.6.2

[phenley]

Rom manager has been golden for me. not to brag just to give confirmation that it is working for someone



Sent from my Droid using Tapatalk

 

[stlcity]

Couple of things with first install:

1. Dont think auto brightness was working for me. THe brightness would not change inspite of having it checked

2. With stock kernel when I turned on wifi it would turn on the wifi hotspot. I could not connect to my home network

3. When tried the wifi hotspot under tethering gave me an error.

4. Maps was installed. But market showed it as "free". Tried manually updating...said install unsuccessful

Using rom manager to install.

Love the ROM though. Trying to wipe again and reinstall. Hopefully I will be able to get it fully working.

 

[bhughesiii]

There have been a lot of issues withclockwork recovery lately as koush is trying to update it to the latest froyo source. I personally use clockwork, thanks to the nifty doesn't have to be named update.zip and it can be located anywhere on the sdcard feature... but my advice to clockwork users, flash back to 1.8.x.x and wait on the 2.0.x.x series to become more stable. Rommanagers also become more unstable as well(for me)

Tried flashing back to 1.8.0.0, in rom manager it says I am on that version, but when I boot into recovery it still says 2.0.1.3...

I may just have to flashback to stock and re-root or find a way to delete my recovery and get sprecovery on there.

 

[Luxferro]

Couple of things with first install:

2. With stock kernel when I turned on wifi it would turn on the wifi hotspot. I could not connect to my home network

3. When tried the wifi hotspot under tethering gave me an error.

You sure you are on 0.6.2?

Sounds like your running 0.6.0, cause I am pretty sure wifi hotspot was removed, and it was documented as removed until bugs are worked out and they get it working with the wifi driver. I don't see it at all in my 0.6.2...

 

[sniffle]

ok guys we have a huge issue... we jsut noticed it... and it is why the kernel file is so huge... in our rush to get you guys the P3 kernel out last ngiht P3 left the debugging symbols in the sourcecode... that means we filled up all of your extra space... which means that's why themes are failing...

we will get the corrected kernel (and maybe a few more for options) as soon as we can. sorry about the oversight on our part

 

[Luxferro]

There have been a lot of issues withclockwork recovery lately as koush is trying to update it to the latest froyo source. I personally use clockwork, thanks to the nifty doesn't have to be named update.zip and it can be located anywhere on the sdcard feature... but my advice to clockwork users, flash back to 1.8.x.x and wait on the 2.0.x.x series to become more stable. Rommanagers also become more unstable as well(for me)

Tried flashing back to 1.8.0.0, in rom manager it says I am on that version, but when I boot into recovery it still says 2.0.1.3...

I may just have to flashback to stock and re-root or find a way to delete my recovery and get sprecovery on there.

Or just learn how to flash recovery over adb. you can find all the files you have selected to download with CWR in your clockwork directory on the sdcard. so look for whatever recovery you downloaded, and had isses flashing back to with rom manager, and do it via adm using flash_image. you just have to look through all the subdirectories in /clockworkmod

People become too dependent on fancy GUI's. They should really learn the basics of adb if they are gonna be messing with their phone constantly.

 

[pdroid]

Been running this without any issues since last night. Excellent job and thanks again to cvpcs, sniffle, and any other Sapphire contributors.

 

[bkd11]

ok guys we have a huge issue... we jsut noticed it... and it is why the kernel file is so huge... in our rush to get you guys the P3 kernel out last ngiht P3 left the debugging symbols in the sourcecode... that means we filled up all of your extra space... which means that's why themes are failing...

we will get the corrected kernel (and maybe a few more for options) as soon as we can. sorry about the oversight on our part

I was wondering why my /system was full. I had to delete a few things just to run the adblock script.

 

[bhughesiii]

ok guys we have a huge issue... we jsut noticed it... and it is why the kernel file is so huge... in our rush to get you guys the P3 kernel out last ngiht P3 left the debugging symbols in the sourcecode... that means we filled up all of your extra space... which means that's why themes are failing...

we will get the corrected kernel (and maybe a few more for options) as soon as we can. sorry about the oversight on our part

Nice catch, was wondering why Luna would not fully install. Looking forward to the updated kernel.

 

[bhughesiii]

There have been a lot of issues withclockwork recovery lately as koush is trying to update it to the latest froyo source. I personally use clockwork, thanks to the nifty doesn't have to be named update.zip and it can be located anywhere on the sdcard feature... but my advice to clockwork users, flash back to 1.8.x.x and wait on the 2.0.x.x series to become more stable. Rommanagers also become more unstable as well(for me)

Tried flashing back to 1.8.0.0, in rom manager it says I am on that version, but when I boot into recovery it still says 2.0.1.3...

I may just have to flashback to stock and re-root or find a way to delete my recovery and get sprecovery on there.

Or just learn how to flash recovery over adb. you can find all the files you have selected to download with CWR in your clockwork directory on the sdcard. so look for whatever recovery you downloaded, and had isses flashing back to with rom manager, and do it via adm using flash_image. you just have to look through all the subdirectories in /clockworkmod

People become too dependent on fancy GUI's. They should really learn the basics of adb if they are gonna be messing with their phone constantly.

I am familiar with adb, just haven't had time to hookup to my laptop to do it.

 

[Tanknspank]

Way to go sniffle.

Can't wait to see what you guys do this time though, because my phones never been so smooth. And who doesn't want new features?

 

[white_ash143]

Is p3droid's kernel missing the 250 mhz slot? SetCPU sets min at 125 then the next is 400...

 

[Tanknspank]

Is p3droid's kernel missing the 250 mhz slot? SetCPU sets min at 125 then the next is 400...

Its probably just what he compiled it with. Froyo handles 125Mhz better than eclair though, so it really shouldn't be a big deal.

 

[white_ash143]

Phone's still slow to wake up even with 125. That's why I prefer 250.

 

[Tanknspank]

Phone's still slow to wake up even with 125. That's why I prefer 250.

Well, my screen off settings are 400/125 and its just fine. But I can see why someone could want it. Maybe p3 can drop the 900 slot in the next release? I doubt many use that slot.

Or maybe p3 knows something we don't. Lol.