it dint show up.bdw i used power search.what if i dont get the answer?if the problem arised after installing K48.i will obviously report it here right?

when you run sudo gainroot
do this :

Just some confirms:
Updated from KP47 to KP48 with HAM. No unexpected problems sofar.
JoikuSpot works if you you apply the old boucerfix.
Nokia BH-214 still doesnt work as expected.
H-E-N works (I think I run BME or atleast default)
Fcamera works.

Edit:
Got the leafpad "Save as"-problem.

Hmm, some here.
In x-term:
root
cd /home/user
leafpad test.txt
(saved the file with some text and exit)
leafpad test.txt
Now I do a "Save as" and 5 seconds later the phone reboots.

Strange.

run-standalone.sh leafpad, i think you meant.

and running leafpad like that does not crash it when trying to use the save as (atleast for me on pk46)

Arghh.. I hate it when I say something and do the opposite.. but WTF, at least it's more or less on topic..

That's true in principle

But if you had looked at the first post (probably you have, just overlooked it you would have noticed the "disabled autoloading bq27x00_battery module".

As far as I know using that module is the only means of getting the battery temperature (I'm sure there's also at least one thread about qcpufreq in this forum, I will leave the proof as an excercise to the reader , so if you don't load that module, so you don't get the temperature.

Now, if it the module is not loaded ("didn't show up") then you need to enable it:

First make sure it is NOT blacklisted. Look in /etc/modprobe.d/blacklist
Then, to be on the safe side, just load it by hand "# modprobe bq27x00_battery" (please report any errors you get).

If all OK, check with the qcpufreq thing and see what you get.

Naa, not for me.
If I run it Standalone I get the savedialog but a few seconds later the phone crash.

I'm willing to bet this has something to do with something plugging into system in an odd way, or a bad parameter being passed into a kernel level call by a library. I don't have my device setup for debugging, but if someone who can get the SaveAs dialog to work in v48 could do an strace and find out what calls are being done, I'd bet good money something's calling in to the same system call in v48 (probably something around getting mount points) with a sometimes bad parameter.

User-based apps shouldn't be able to crash a system this readily. There's got to be something happening at a kernel/system level to cause this quick of a reboot on multiple people's systems.

cant see the temp using desktop execution command widget, works fine in qcpu
any ideas?

sorry if smeone already said it, cant read all the 10000000 posts and didnt get answer using search or at least didnt see it
cheers

how I can regain the kernel V47?

kernel-48 battery discharge so fast I