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.
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
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
Hello,
I got an problem on like 4 of the 5 kaisers here.
The problem is that sometimes the kaisers goes into an sleep where it doenst come out without reset.
You will get an black screen and the light of your keyboard is on and doesnt turn off. When this happens the battery goes from 100% to 0% in like 40 mins. without the problem i can use the phone for 2 days.
My question is how to solve this? I tried the following things.
- Radio 1.65, 1.70. 1.71
- 2 different hspl
- old and new kernel.
- and loads of different roms. from gingerbread to eclair.
Any solution or fix for this? because i can't use it for daily base now since when i dont notice the battery is empty of that bug.
Best Regards,
Veldmuus
That's the black screen of death. I never get that, but it's one of three problems that I have heard of. I think it might be related to going to sleep. I use the latest kernel, from git, which is pretty much identical to scooter1556's kernel with separate cache. What kernel are you using?
The second problem is the white screen of death, which I get a lot when I leave the phone on the charger. The screen is white bright, the kernel is not crashed. Sometimes Fn-Right-soft-key twice will cure this, but usually not. Some have guessed that this has something to do with the phone going to sleep not quite properly while charging. There is an option to not go to sleep while connected to a charger, and I haven't tried that option for a long time.
The third problem is a kernel crash (screen freezes, keyboard doesn't turn on LED, etc) caused by compcache (zram). Can be avoided by not using compcache.
The most annoying issue I have is that I've never figured out how to tweak the build so that apps can be installed to SD. I've been trying to change initrd so that, when installed completely on NAND, the sdcard is completely managed by vold. So far no success, and I've pretty much moved on to my newer phone (Rhodium, aka AT&T Tilt2).
I have spent the last week or so "tweaking" my build.prop file, adding lines for disabling sleep mode, 3G speed tweaks (doesn't do much yet) and fixing small compatibility issues such as AGPS/GPS not working. So far so good, no more sleep of death/black screen/white screen.
If successful, I would ask that the modified build.prop file be added to the Froyo builds on SourceForge, intergrated directly as to eliminate "end user interaction", meaning you won't have to touch it.
I am also looking into some sysinit.rc mods as well, but I haven't had much time lately.
Veldmuus, do you have a way to edit your own build.prop file such as Root Explorer, or would you have to push it to the phone via ADB?
I have found NO info on my problem. I flashed cm7 to my EVO a couple years ago and I tweaked settings in menus a rookie shouldnt have been in. I used auto-starts to stop user & system apps from starting up and for whatever reason when i flash a new ROM it reverts start-up permissions back to my customized settings & not the factory specs. It isnt even every single setting I adjusted. Its a specific few apps & after flashing a new ROM I can get the permissions to stay clean allowing start-ups on all but two that i am aware of. The apps that, im aware of, the start-up permissions system default is turning them off after a new rom flash are Amazon(3or4 permissions Xrossed out), Dialer(1x), Email(1or2x) FM radio(1x), calender storage(3x), market updater(1x), the orginal market(1x) the current Play store(1or2x), Google services framework(1x), & I think thats all of the ones that i can adjust to start-up in an auto-start manager app after a new ROM flash following a reboot and the permissions staying clean & not Xrossed out. Then there's my 2 NIGHTMARES, GOOGLE 1 TIME INITIAL(1x) & GOOGLE PLAY SERVICES(7X). The auto-start permissions for these 2 apps will NOT stay adjusted to on after any new ROM flash or reboot or hot boot following their permissions reset.. One of the (corrupted maybe?) auto-start permissions that wont reset for Google Play Services is connectivity, meaning changes in signal connection(e.g. wifi, 3g, airplane mode) &/or plugged-in charging and un-plugging the phone. In turn, when I plug-in my EVO to charge, things get extremely buggy. U/I jumps & absolutely arrogant acts of erratic behavior. Touch points on the screen don't match up. Choppy animations. Apps begin to respond like they have consumed all of the resources available and if I am lucky they just lag ,on average, 5 seconds behind & many just finally give up and force close. However, once I un-plug my EVO things assume a 90-95% stable activity with "almost" no sign of any previous problems. I have tried every combo of wiping, mounting/unmounting, settings on/off, booting, & flashing I could think of trying to fix this problem. i flashed sense based ROMs and AOSP ROMs as well as stock builds along with every kernel combo xda had available.. I was CONSUMED for 20 straight hours this past Friday alone in this mess. Over the last 6 days Ive invested over 100 hours in tweaking setting combos along with wipe, mount/unmount & flash combos. Please hElp, I just want my EVO to recognize its own "Roots" again. L2ms... The Nand backups I did 3 years ago at the pinnacle, of this misery my EVO lives in, are on a hard drive that is LONG gone.. I am capable enough to know where the answer to my situation rests.. It surely will NOT come from a noob, nor will it not come from a mildly talented android user or any mediocre devel, It wont even come from a trained android tech. The Help(01101000 01100101 01101100 01110000) I seek will ONLY be supplied by someone who bleeds green, someone who also speaks binary. He Has Intelligence & IntelliJence.This person doesn't 'think things through', He "Processes Information"... That is the Professional Android Developer who holds my well being in his hands.. I seek The One who is the Android Alpha/Omega Eminence.... What follows is my binary plea for help,,
01110000 01101100 01100101 01100001 01110011 01100101 00100000 01101000 01100101 01101100 01110000 00100000 01101101 01100101
Please excuse my accent as I am just learning binary