http://forum.xda-developers.com/showthread.php?t=951981
Got FRX04 working on my blackstone nicely - has anyone updated to FRX05 yet?
I have.
Changed kernel yesterday to the last autobuild one, with cam libs - Everything ok.
Today I changed system.ext2 to FRX05, deleted libs, modified froyo.user.conf - Same behaviour. I feel it more responsive, can be placebo. But cam definately works faster.
BTW, do you get sound with camcorder? I do...
Hi Eodun,
I'm using FRX04 right now. To upgrade to FRX05, all I have to do is replacing the system.ext2 file right?
It seems you mentioned multiple things to replace? I'm a bit confused. Please explain.
So, the overall system is more responsive, or only the camera?
I don't use the camera that much, but its nice to have it works, when Skype Video comes out, hope that will be useable.
Lothaen said:
http://forum.xda-developers.com/showthread.php?t=951981
Got FRX04 working on my blackstone nicely - has anyone updated to FRX05 yet?
Click to expand...
Click to collapse
FRX04 works nicely on Blackstone indeed, with a few startup.txt entries added to overclock, prevent 'waiting for sd' and keep it out of deep sleep.
I used the one from the babijoee thread
I only had the camera working once (pics and video) but i can't remember if it was FRX04 with viruscrazy's camera modules/libs or the Froyo X Red distribution. Been swapping modules and complete bundles so much, need to start keeping logs.
Currently testing Gingerbread but will have a go with the FRX05 systemext2, and see what modules run best.
@Eodun:
last autobuild one, with cam libs
Click to expand...
Click to collapse
and
FRX05, deleted libs, modified froyo.user.conf
Click to expand...
Click to collapse
means all separate things, right? Or if i want to try this do i have to go into the system.ext2?
one more question, is replacing the system.ext2 file will cause the entire system becomes new again? (I mean will it retain the applications that have been installed, and the user data, provided the user data file remains there.
Thanks!
lie_ui said:
one more question, is replacing the system.ext2 file will cause the entire system becomes new again? (I mean will it retain the applications that have been installed, and the user data, provided the user data file remains there.
Thanks!
Click to expand...
Click to collapse
If I'm not mistaken, all settings and apps are in the data.img
lie_ui said:
Hi Eodun,
I'm using FRX04 right now. To upgrade to FRX05, all I have to do is replacing the system.ext2 file right?
It seems you mentioned multiple things to replace? I'm a bit confused. Please explain.
So, the overall system is more responsive, or only the camera?
I don't use the camera that much, but its nice to have it works, when Skype Video comes out, hope that will be useable.
Click to expand...
Click to collapse
If you had the camera working with the test kernel, then yes, do as I say in my post. You will need the last autobuild kernel and to clean froyo.user.conf from ln and mount --bind statements besides the new system.ext2, as everything about camera is included there.
hrk7474 said:
@Eodun: and means all separate things, right? Or if i want to try this do i have to go into the system.ext2?
Click to expand...
Click to collapse
Yeah, 2 different tests.
The best way to go, anyway, is to keep data.img and ts-calibration, wipe andboot folder, get FRX04 full bundle, replace system.ext2 with FRX05 one and restore the first files to andboot folder.
That way you'll have a pretty clean install. If any problem, as always, first thing is to backup data.img and see if it works with a new one.
BTW, how's your battery performing?
Tonight I left it fully charged. After 6 hours, it was at 56%. So 44% spent with phone unused at all (but wifi and sync was on, as I received mail).
Hi,
I've updated to FRX5 yesterday, and so far much better/faster than FRX4.
Camera and camcorder works fine.
Battery life for me is similar to FRX04.
The old issues still unsolved (at lest for me) are:
a) Bluetooth not working (for me the most important to use it on daily basis):
- Calls: even if paired with my handsfree, and you pickup the call with it, voice is not going throught the handsfree.
- Music: it goes thorugh the handsfree, but suffering heavy audio shutering.
b) Skype not signing in.
c) Facebook don't sync contacts.
Brgds
ypsmav said:
Hi,
I've updated to FRX5 yesterday, and so far much better/faster than FRX4.
Camera and camcorder works fine.
Battery life for me is similar to FRX04.
The old issues still unsolved (at lest for me) are:
a) Bluetooth not working (for me the most important to use it on daily basis):
- Calls: even if paired with my handsfree, and you pickup the call with it, voice is not going throught the handsfree.
- Music: it goes thorugh the handsfree, but suffering heavy audio shutering.
b) Skype not signing in.
c) Facebook don't sync contacts.
Brgds
Click to expand...
Click to collapse
a)BT as always... still no devs onto it AFAIK
b) That's Skype's problem, not XDAndroid. There are other original Android devices that can't login too.
c) Not sure where the problem is, but same as a). Could be google's problem too.
I updated my blackstone to the FRX05 last night. First, I only replace the system.ext2 file within the existing andboot folder and after booting it up, it was so slow (both booting slowly, and once booted, everything run so slowly).
Then I followed advice from Eodun to backup and deleted the andboot folder, and put back a new andboot folder from the FRX04 plus the new system.ext2 file from the FRX05, and put back the data.img and the calibration file.
Then boot it up, it runs normally now. Everything seems to be back normal, it runs smoothly and may be a bit faster than FRX04, but not really significant faster.
I was glad it runs normally again and could pick up the old data.img, so I did not need to reconfigure everything.
Camera does not work for me. Eodun, it seems you just mentioned few more steps to get it working? Can you give more details on those steps?
I also notice the startup file did not have the rel_path=andboot anymore.
But it seems no problem at all, mine runs fine without it.
Well, now you just need to get the lastest kernel from autobuild and cam will work out of the box. http://glemsom.users.anapnea.net/android2/htc-msm-linux/
About rel_path, better having it, just in case haret goes mad
hmm.. i downloaded the kernel but have not figure out how to expand the tar file and get the kernel file out of it (I don't have linux). Perhaps I should wait until they release a full bundle of FRX05.
I use 7zip file manager for windows, it can extract tar files and it's free.
BTW, remember to:
1.- rename zImageblahblah to zImage
2.- Don't extract modules
3.- Put both files in andboot folder (overwrite zImage)
4.- You can safely delete old modules (be careful with which ones you delete! )
Clean install on formatted SD
Since this turned out to be a rather lengthy post, there's a conclusion at the bottom of it. And if all your interested in is camera performance that's where to go...
FRX04 bundle with FRX05 system.ext2 and 20110228 kernel on a freshly formatted SD.
(and with old startup.txt: OC, waiting for SD fix, initrd_offset, sleepmode 3)
First boot:
Get's to home screen. Started removing widgets, and at the last one (search bar) the phone froze.
Waited for a few minutes, then pulled battery.
Second boot:
Boots fine until lock screen. When unlocking phone it had removed all home screen widgets.
Went to APN settings to remove the defaults loaded from SIM which are wrong, but phone froze as soon as i touched the menu button inside APN properties.
Waited for a few minutes, then pulled battery.
Third boot:
This time without SIM since the problem with the second boot so closely resembled the freeze of the froyo x red first boots issue.
Boots into lock screen. Straight to APN settings. No freeze
On to Wifi settings. Setup and connected in no time at all!
Setup Gmail account. Synchronized without problems.
Went through most other settings without any problems. Happy to see the time-zone issue is now fixed
Read some email. Wifi is working great, just like before. Wanted to play some music but realized there were no mp3's on the sd...
Oh well, time to put in the SIM. Phone shut down 'as designed'.
Fourth boot:
With SIM, also put some apps to install in designated folder (including ZEAM) and some mp3's in a separate folder.
Boots into lock screen. Unlocked and set ZEAM as default launcher. Loads fine. Very responsive and fluid. (i turn all animation OFF)
Played some music: stutters unbearably...
Disabled Wifi, opened an email to connect 3G. Message opens, but (probably) prefetched because there's no 3G icon in the notification bar.
...Freeze...
Waited for a few minutes, then pulled battery.
Maybe i hadn't switched on 3G in WinMo before this boot, don't remember or know if it's still needed. Turned it on just in case before the
Fifth boot:
Just to see if audio is ok without Wifi. (i had this with some other kernel, don't remember which one, really should start keeping those logs)
While watching the androids fly through the boot animation it hit me: i never put the dot next to the APN after inserting the SIM again...
Freezes after i pull down notifications...
No waiting this time.
No changes, just a
Sixth boot:
Starting to lose confidence in this endeavour...
Boots fine, unlocks fine. Into settings, and freeze...
Lucky number 7 or tie-breaker?
Removed the OC from startup.txt, even though it's 'only' at 600Mhz and never gave me problems with other builds.
Boots fine, unlocks fine. Into settings to find the default APNs are back alongside the one i put there myself and the dot next to the wrong one.
Put the dot where it should be, deleted first excess APN, deleted second excess APN and freeze...
One more time...
YES! The 3G icon is there.
BUT! Still stuttering the audio.
Check out the camera though before swapping kernels: it loads.
After taking one picture i get an all black viewfinder. Phone's not frozen because it vibrates when pushing the virtual buttons. Back button does nothing, but it let's me turn off the screen and back on again to find the lock screen. Camera not running anymore according to task killer. Try again...
Now it let's me take pictures. AND record video, with sound. The first picture i tried to take is not in the Gallery.
Conclusion:
Although it took me 8 boots to finally have this FRX05 system.ext2 running, it runs very well once it does. Praise for implementation of the camera in the last kernel, pics and video with sound, hooray!
But because of the audio, this kernel is not for me.
I'll try once to get it running with the 1255 kernel and otherwise it's back to GBX0A for me.
I always have to let settle down and load everything (just wait 2-3min) after a boot. After that, I have none of the problems you describe, though I don't play music and don't know about the stuttering (sure it's there, as it's a problem with battery meter). Oh, and I don't use 3G...
You must have something around that makes your device behave weirdly.
First thing is OC, I never felt that it made my phone run faster, but to decrease stability.
Also, if you tried many builds, one thing I'd do is to beckup, full format SD with HP format tool and restore.
Thanks for your tests
Thanks for reading all that
I just did the kernel swap to 1255 and the audio stuttering is gone, but of course so is camera functionality. I'll try to put in the libs from viruscrazy's thread to see if it works sometime tomorrow. For now i'll just fully charge the battery and see how long it lasts. I had GBX0A running for over 12 hours without charging with this same kernel.
You must have something around that makes your device behave weirdly.
Click to expand...
Click to collapse
Well, yes. That would be me
I haven't put back the OC, and like you said, i can't really tell the difference. I'll just leave it standard for now.
I've made backups of working FRX04 and GBX0A builds with everything on them, because i format all the time
I'll keep testing and trying things. Thanks again.
aaarrghh made a full bundle with FRX05, you can find it here: http://files.xdandroid.com/FRX05_Full_Bundle_3.3.2011.zip.
For blackstone just remember to keep ts-calibration and startup.txt, also data.img if don't want to lose everything.
I had issues with the calibration using the FRX04 full bundle and adding on the FRX05 system.ext2
kept coming up wit the calibration question then as soon as i pressed the first one it went back to a screen full of text so i had no idea where to press...
trying the frx05 bundle now...
edit: same issue - will go back to frx03 and hopefully it will work on there and i won't delete it this time and copy that to frx05!
tried the GBX release too which did the same calibration issue
edit2: calibration for my blackstone:
155,921,866,922,509,548,145,175,865,168
just in case it helps in the future
Related
I am using Myns Android ROM withthe wifi update + 110 pixel density update, booting via SD card and every now and then I get a graphical glitch/system crash that shows as thin, black and white stripes on my screen.
Anyone know what might be the cause/how I can fix this?
If i chose to install to NAND, would it be more stable/faster? And can I simply flash it with a WM ROM to go back to "normal"?
Thanks!!
I cant say about the glitch, try changing the kernel maybe. But your second and third questions have been asked and answered so many times, its ridiculous. But since its your first post, I'll answer:
would it be more stable/faster?
Click to expand...
Click to collapse
Yes to both
can I simply flash it with a WM ROM to go back to "normal"?
Click to expand...
Click to collapse
Yes again. Also, Try using the search button in the forums, and read the stickys, go through some threads etc.
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
graphical glitches are usually caused by using the wrong panel type in default.txt when using haret, or the wrong NBH panel type when using Nand, to fix the first, edit default.txt, to fix the second flash another NBH with another panel type, (panel type is usually in the filename).
To remove a widget, press and hold on it, then move it to the bottom of the screen.
Apologies for being a totaly newbie, but what are the "panel types"? MY default.txt shows the correct resolution, but I cannot see anything about panels (I might just not be looking hard enough lol!)
I now have a problem when booting from the SD card that my resolution is "bigger" (icons are larger and overlap, menu items are larger too) But it was fine before i rebooted....
Any help for the GPRS issue?
mr_pablo said:
My apologies for not going through the threads properly.
I half knew the answers to my 2nd and 3rd question, but wanted clarification
I am trying Super Eclair Lite, and whilst wifi works well, I cannot hook up to 3G(gprs/wap/hdspa/EDGE etc)
I can call and make/receive texts though :S Hit this glitch a couple of times too, but i noticed it seemed to happen when putting the device to sleep, so I changed the screen setting to 30 minutes and turned of animations etc.
p.s. How do you remove widgets?
Click to expand...
Click to collapse
You can remove widgets by long pressing on them until the bottom tray becomes a bin/x or something similar, then drag them to it.
About the 3g problem, I had that a while back after installing a new build, what solved it for me was changing the kernel. I had flashed to nand so I simply got another nbh. For you it might be zimage. If you say you got that graphical glitch when the device went to sleep, then you should try changing your panel time. For a good smooth android experience, you will have to take some time, and flash many different nbhs/updates and change settings etc to get what works best for you.
I am trying out Myns Warm Donut again with the wifi update.
How can i change panel time?
Dunno if this helps but I managed to get GPRS/3G working on SuperEclair. I had to manually put in the APN and made sure the mcc mcn codes were right.
When i changed the codes the APN disapeared from the list but data connection established itself after a couple of minutes.
This is the link I used to get the right APN codes:
http://george.insideiphone.com/wp-content/uploads/2007/12/mcc-and-mnc-codes.pdf
For NBH files the panel type and resolution is in the filename: KAISIMG-PANEL1-320-ECLAIR.NBH : the filename shown is for Panel1 resolution 240x320.
To change panel type simply flash another NBH with panel2 or panel3, it will not affect your install, since the android nbh's don't format Nand, this is done by the installer
For Haret installs the panel type is changed in default.txt look for the line: board-htckaiser.panel_type and change the value to 1, 2 or 3.
Wow, that is great! I've searched for a solution for this problem a long time, but this is the first thing that works for my Kaizer 130.
Many thanks!
I had android running off the sd card most of the day yesterday, using the panel type of 1 worked well (did notice the odd glitch when coming out of sleep mode, but it didnt crash)
still not sure what the panel type does, can anyone explain? (curiosity really)
However, I tried to use the camera, and after switching to vide and back again to photo mode, android crashed.
I can suffer not using the camera, as its nothing amazing.
p.s. anyone know if you can remap the buttons? as the hang up button puts the phone into sleep mode, the wheel doesnt do much, and other buttons dont do much either.
Panel type refers to the LCD panel, there are 3 different types of panel fitted to the kaiser series, one manufactured by Sony, the other two by Topoly, functionally they are identical, however there are some differences in the electronic controllers fitted to each, which in winmo is detected automatically, however Android is unable to detect the differences and the correct type must be passed to the kernel at boot time, either by boot parameters in default.txt or hardcoded into the NBH. Due to the way electronics factories work, the panel type depends on which one was available at the lowest price, and shortest lead time, when it was required, hence the reason for the confusion, since some people still think that panel type is set for certain models of kaiser, which is inaccurate, since both my KAIS130's have different panels fitted.
Camera does not work in any Eclair build yet, it does in Donut builds, however it's still a little low quality even on the 3Mp Kais130, Video does not work on any android builds very well, if at all.
Remapping buttons can only be done by recompiling the kernel I think, however after a while the button layout becomes second nature, I actually get lost using winmo now, lol.
im running xdandroid BLAZN on my rhod210 and im using the latest kernal. And apps wont install anymore from app market or through apk installer. Even apps that are already installed if you uninstall them they wont reinstall. Anyone else having this problem?
also my home/power button still isnt doing its designated function of bringing me to home screen? this problem occured about 5 updates ago so shouldnt it be fixed? iv heard its literally a one line change to fix this.
And does any1 else think that stability has decreased in the latest kernal updates? if i play music so i can hear when it goes off, i get sleep of death every 3minutes when in sleep mode. Also android restarts to splash startup screen regularly which is annoyn as incoming messages are rejected when this happends.
Wow... Let's try to break this down. The home/power button switch was intentional... so it's not going to get 'fixed' as you say. See this thread if you want to revert the commits in question that change the button layout.
App/market issues are almost always fixed by deleting your data.img and starting clean - this will wipe all user data off of the phone, you'll basically be booting for the first time again as far as the system is concerned without a data.img.
Stability... it's like battery life - perception is everything. I wouldn't say the new builds are any more or less stable than the previous ones, no. In fact, I would say they're more stable, but that's just me.
+1 What arrrghhh said!
We're most fortunate to have arrrghhh.
I also find stability has continued to improve with most kernel, modules, & rootfs updates including the most recent.
I can only add that until Sov updates to the Froyo [2.2] [25-10-10] System.ext2 in his Blazin build USE his Reference build. And if you must overclock at least DON'T when your building a new data.img file.
I get considerably more SOD & other abnormalities when overclocking at any level.
tank you arrrghhh and LDgator.
My app installation problem started when i updated the kernal so i presumed that was the problem but if im the only one with this problem then its more than likly my data.img, i will move and rename my data.img have it create a new one to check of that is the problem and iv been using blazn because i presumed it would be updated soon after reference. But its been awhile now so yeah maybe i will switch to reference for the time being maybe will solve my stability issue's.
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
lemminman said:
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
Click to expand...
Click to collapse
Camera not working is related to your kernel/radio rom. Also you could use not so super froyo if you want the same with more features. If you want more speed I suggest a Cyanogen based rom as these are the fastest currently. I suggest changing your kernel to l1qu1ds latest .32 kernel via the thread that is stickied at the top.
USB to pc is not working through my computer right now but adb is at least. What I do for data transfer is just use System on NAND and Data on SD and use a card reader for the data.
Lastly, remember that android on the Kaiser is by no means perfect and is still more or less of a thing to be like "Look what my old phone can do!" thing. If you want everything perfect then Windows mobile has that already. Otherwise if you want a cooler newer OS on your phone then its going to take a little time for us. We have come a long ways but not all the way there yet.
lemminman said:
I just flashed my Kaiser with Fat Free Froyo RLS5. I really like the Android OS, but the lack of functionality is bothersome. I can't type into the Google search bar that is on the desktop, the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor. I've only been using it for about an hour and already found all these problems so I can image that there are more.
All I am looking for it a version of Android that will allow me to use the camera, browse my SD card from my PC, and has a working WiFi. Speed is also a concern.
If I could get some suggestions I would be appreciative.
Thank you.
Click to expand...
Click to collapse
the search bar will work if you download google search from the market, it was removed since it can be installed from the market, fat free is fully functional you just have to work to get it going out of the gate, now in contrast not so super froyo is ready to go from the get go
lemminman said:
the camera doesn't work and, worst of all, the USB to PC data connection is inoperable. These things along with some other minor things like the fact that I can't change the volume of the alarm clock make me want to try a different flavor.
Click to expand...
Click to collapse
I am using Fat Free Froyo RLS5 and all that stuff works for me.
USB to PC works perfectly in linux It works for me on windows 7 too, but you just have to wait a long time (maybe 2-5 mins) for the computer to recognise it.
To change the alarm volume just roll the jog wheel while in that menu (or press whatever buttons you have assigned to volume up/down)
Thanks for the help, guys.
I suggest changing your kernel to l1qu1ds latest .32 kernel via the thread that is stickied at the top
Click to expand...
Click to collapse
That is the kernel I have. My radio is version 1.65 something.
What I do for data transfer is just use System on NAND and Data on SD and use a card reader for the data.
Click to expand...
Click to collapse
I don't have a card reader; that is why this is important to me. Are there any Android versions that this works, or an app that I can install even?
Lastly, remember that android on the Kaiser is by no means perfect [...]
Click to expand...
Click to collapse
The only reason I don't want WMP is because it is ridiculously slow to respond. I had heard that Android was much faster so I am giving it a try.
the search bar will work if you download google search from the market
Click to expand...
Click to collapse
That part really isn't a big deal; I probably would never even use it. It was just one of the many small glitches I was noticing during normal use. Things like there being no way to bring the phone back from sleeping except the power button (not even opening it!). At one point, when it is just sitting on my desk, the screen turned white and the phone was completely unresponsive. I had to hard reset it. They keyboard works except when dialing a number where it seems completely random.
If there is a workaround to these things, I'm fine with doing some personalizing, but if not, I would like to know if there are flavors that don't have these kinds of issues.
I think I will try Cyanogen like you suggested and see if I like it any better.
Thanks again for the help.
lemminman said:
Thanks for the help, guys.
That is the kernel I have. My radio is version 1.65 something.
I don't have a card reader; that is why this is important to me. Are there any Android versions that this works, or an app that I can install even?
The only reason I don't want WMP is because it is ridiculously slow to respond. I had heard that Android was much faster so I am giving it a try.
That part really isn't a big deal; I probably would never even use it. It was just one of the many small glitches I was noticing during normal use. Things like there being no way to bring the phone back from sleeping except the power button (not even opening it!). At one point, when it is just sitting on my desk, the screen turned white and the phone was completely unresponsive. I had to hard reset it. They keyboard works except when dialing a number where it seems completely random.
If there is a workaround to these things, I'm fine with doing some personalizing, but if not, I would like to know if there are flavors that don't have these kinds of issues.
I think I will try Cyanogen like you suggested and see if I like it any better.
Thanks again for the help.
Click to expand...
Click to collapse
the white screen is a known issue apparently overclocking improves this
White screen is present when the system didn't draw the screen before it power up.
When you overclock the system is faster so it spend less time to draw the interface.
Sometimes you have with screen when the system sleep but it can't resume because the main app crashes.
To change the alarm volume just roll the jog wheel while in that menu
Click to expand...
Click to collapse
This changes "Ring volume" regardless of what I have opened.
Thanks for all the input, everyone.
I have tried four different Android builds now and I haven't gotten a USB data connection with any of them. I noticed that one of them had a Network option, as though I might be able to browse files of computers on the network which would solve my problem. Unfortunately, that particular build just says "Error" when I try to turn WiFi on.
Is there an android app I can install that will allow me to transfer files between my phone and a PC? That is really the number one priority right now. To test these Android builds I have been reverting back to WMP every time I want to try a different one because I need to put the androidinstall.tar onto my card. I tried loading a bunch of different ones on the card to avoid this, but I get "Permission denied" when I try to rename a file in the andboot folder.
Thanks again.
The forum search tool will answer all those questions I know I have answered it atleast 500000 times
Sent from my HERO200 using XDA App
I have a kaiser with froyo kernel 2.6.32 date 9.9.2010 I have overclocked with atools to 500 mhz and also overclocked the GPU, battery is standard setting. My radio is Neon 1.65.24.36 Together with thoughtlesskyle`s (thank you!!) fat free release 5, i have a very stable situation here. I have to admit i am not a heavy user. Merely phonecalls and sms (or whatsup) and sygic navigation software . I only have to reboot once a week. I am not sure why, maybe because i use cachemate once a while.
For connection between pc and kaiser i use SD Share Dual Mount. It works perfectly. I had flashed the latest kernel(s) of l1q1d because of the alleged stable reboots. I am sad that i did not have stable reboots, it got stuck and i had to reinstall my apk`s again. And most important for me, the SD Share did not work with the latest kernel(s), thats why i reverted back to the 9.9.2010 one.
As for the white screen, it only happens to me if my kaiser goes asleep and i awake it immediately. If i take some seconds between asleep and awakening, it`s okay.
I have to thank many people here to be able to use my kaiser like i bought it yesterday or so. Maybe someone can try my settings and profit from it, like i do.
Shayer said:
I have a kaiser with froyo kernel 2.6.32 date 9.9.2010 I have overclocked with atools to 500 mhz and also overclocked the GPU, battery is standard setting. My radio is Neon 1.65.24.36 Together with thoughtlesskyle`s (thank you!!) fat free release 5, i have a very stable situation here. I have to admit i am not a heavy user. Merely phonecalls and sms (or whatsup) and sygic navigation software . I only have to reboot once a week. I am not sure why, maybe because i use cachemate once a while.
For connection between pc and kaiser i use SD Share Dual Mount. It works perfectly. I had flashed the latest kernel(s) of l1q1d because of the alleged stable reboots. I am sad that i did not have stable reboots, it got stuck and i had to reinstall my apk`s again. And most important for me, the SD Share did not work with the latest kernel(s), thats why i reverted back to the 9.9.2010 one.
As for the white screen, it only happens to me if my kaiser goes asleep and i awake it immediately. If i take some seconds between asleep and awakening, it`s okay.
I have to thank many people here to be able to use my kaiser like i bought it yesterday or so. Maybe someone can try my settings and profit from it, like i do.
Click to expand...
Click to collapse
Well at least the white screen is being worked on, see the thread I made.
Hi everyone!
So far for the past 2 years I have been running various builds of Android on various Kaisers (yes, I have 4 of them now).
For the past 6 months or so I have stuck with the 2.2.2 build from SourceForge (system_froyo_us_odex) and never had any issues... until now.
All of a sudden, for the past 2 weeks I have been getting that dreadful "sleep of death" problem, sometimes upwards of ten times a day!
Current installation is as follows:
Scoot cache kernel, 15mb cache, 500mhz, ext4, 1500mah battery.
Froyo 2.2.2 US Odexed from SF with all the stock apps, extras listed below
ADW EX Launcher ver. 1.2.2
Beautiful Widgets ver 3.3.4 with the animation package (Super clock 4x2)
Rogue tools
Root explorer
Scanner radio (barely use due to constant data usage)
Pandora (again, data usage can be high so barely used)
Facebook ver 1.8.2 or current build
Foursquare ver 2012.02.27
I have looked at dmesg on the SD and compared to one from a backup SD but cannot find anything extraordinary, nor is there anything wierd in /system/sysinit.rc. Performed a complete wipe and reinstall from stock with all the same apk's and even changed to the brand new (turned on once) Kaiser after unlock/SPL install.
If anyone sees anything out of line (except the BW 3.3.4, I like my flip clock), please do let me know. If there is any files you may need from either the phone or SD card I can paste them accordingly.
Okay, made some line entries in build.prop via root explorer's text editor and added the line "ro.ril.disable.power.collapse" with the argument set to 1, which should have turned off any sleep mode, and also added the line "pm.sleep_mode" with the argument set to 1. This after doing a search on google for build.prop tweaks (there's a bunch).
Battery life has suffered a little but it seems to have helped somewhat. It will still hard lock in sleep mode and be unresponsive until a stylus reset or battery pull.
I got an equal issue after inserting pm.sleep_mode= in my startup.txt for haret. Sometimes the 'sleep of death' and sometimes never ending boot circles. The only argument working is the default value '1'
What I ended up doing was to go back to scratch. This happened on 2 separate phones by the way so the spare was the guinea pig.
I started with the kernel first, rebuilt it and reinstalled it, then installed a clean froyo build, which would still hard-lock.
I went back even further and reflashed the SPL, then rebuilt the kernel as before and another new froyo install, which seemed to work. I then copied what I did on the spare and refreshed the newer phone and synced my accounts to it, then reinstalled all of the apps, one at a time, to make sure there wasn't one causing this.
So far so good, no SOD or hard locks.
Went in and re-edited the build.prop to add some performance mods (dalvik.vm.startheapsize=4m, dalvik.vm.heapsize=32m, etc)... seems to be better, smoother and doesn't FC apps as much.
We shall see what happens...
Well, since you can't find this post on the front page, I'll have to put up a new post about my build.prop changes that really help with speeds and FCs'.
Look for it on the front page...
Firstly, outstanding work by vijendrahs on this ROM. He's breathed a huge amount of life back into the Desire. I really like the phone, but was hitting the memory ceiling pretty hard. Memory worries are now a thing of the past! Props, and many thanks.
In case any devs monitor the Q&A, here are a few issues I found with the 2.7 release:
1. Dolphin Browser (both regular and mini versions) crashes reliably upon opening two or three tabs and switching back and forth between them two or three times. It does not matter whether caching is set to SD. Curiously, the built-in browser does not have this problem, and I am therefore tempted to blame Dolphin ... except that this is not a problem in 2.51. (I went straight from 2.51 to 2.7, so I don't know if this issue exists in 2.6.)
2. The update process killed my radio. Had to do a full wipe, reformat the SD card, re-create the sd-ext partition and reinstall everything from scratch.
3. I took a couple of pictures, put the phone in my pocket with the screen off, and about 90 minutes later my battery had dropped from about 90% to 28%. The battery stats showed the screen had used 50% of the CPU time and the Gallery app had used 20%.
4. I disabled the Gallery app, just to see what effect that would have on battery life. Both Gallery and the camera disappeared from the home screen and from the apps list, and neither shows up as disabled when I go to manage apps, so I can't simply re-enable them.
By the way, I created the sd-ext as ext4, which I have read (here or elsewhere) can be buggy with CM10 in general or the Desire in particular. I'm going to try ext3 and see if that makes any difference.
Hope this helps someone!
Does anyone have a problem with the camera?When I turn on the camera, it all becomes a colorful throws lines etc.
Camera is a known issue
kimisu said:
Does anyone have a problem with the camera?When I turn on the camera, it all becomes a colorful throws lines etc.
Click to expand...
Click to collapse
That's a known issue. Just turn the camera on, turn it off, and turn it back on, then it will work fine.
PatC11 said:
By the way, I created the sd-ext as ext4, which I have read (here or elsewhere) can be buggy with CM10 in general or the Desire in particular. I'm going to try ext3 and see if that makes any difference.
Click to expand...
Click to collapse
Ext3 vs. ext4 made no difference. Another issue:
5. Skype does not release the mic back to the OS (i.e., the phone) after ending a call. Have to reboot the phone to get the mic back. Could be Skype's problem, I suppose. I've seen an .apk to fix this for Nokia phones, but don't know what it changes.
PatC11 said:
That's a known issue. Just turn the camera on, turn it off, and turn it back on, then it will work fine.
Click to expand...
Click to collapse
thanks for replay,
I/O scheduler
Hi,
Does anyone of you guys here have problems with changing the I/O scheduler?
It is stuck at "deadline" and I would like to try to change it to "noop", however, it does not respond to my input.
I've read at developer thread that some users had this problem but it remained unanswered...
One more question, how to fix LED flashlight for msg?