Related
Installed everthing as per instructions on my SE X1 : http://forum.xda-developers.com/showthread.php?t=1156421
First time starts smooth - after doing CWM recovery of Honeycomb..v3
Wifi works.. browsing works.. etc.
I powerd off using the power off option..to reboot and installed gapps.
Now on its keeps rebooting anywhere during booting process.. sometimes it would come to the honeycom moving screen and then reboot.
I reformatted and tried everything again - 4 times now.
It is stable when gapps is not installed??
Any other way to install gapps? other than by CWM recovery method??
Or am I doing something wrong here..
I am very new to android installation.. please help
you should ask this in the rom-thread, not here. if someone comes to "question & answers" about x1, he doesn't expect questions about a half-ported OS, right?! (it's a winmo-phone...)
but yeah, you're doing something wrong. never had this problem when using honeycomb v3. which gapps-zip are you using? the one needoo uploaded?
anyway, better head over to neopeek and get neofroyo v0.1, it's much better. looks like needoo has a new version coming too, based on neofroyo.
Thank you for your reply..
Newbee to XDA so no permission to post in those threads...
However evrything is working now...wifi, apps.. maps.. etc.
hopefully once I am used to getting around these things will take ur advice and try neoFroyo V0.1.. Sure
oh, i always thought that 10-posts-limit only affects the "real" dev-forums. sorry.
I was checking out Live Wall papers from the Market.. Nothing seems to be compatible with HoneyComb Froyo V.3
Does anyone know any that may be compatible..
Ofc it does drain your battery..
simply put best android for x1
neofroyo has wifi issue and not even close to as sexy as honeycomb v.3 is
maybe your installing wrong gapps i never had that issue either
what kernel are you using as well
i found that the only kernel the worked perfect was ygge's turbo
No wifi-error on neofroyo with ygge-kernel. Midnight's kernel works too, but battery-charge isn't shown yet. But it's fast...
Neofroyo is faster than honeycomb, but let's see what needo comes up with next.
caliban2 said:
No wifi-error on neofroyo with ygge-kernel. Midnight's kernel works too, but battery-charge isn't shown yet. But it's fast...
Neofroyo is faster than honeycomb, but let's see what needo comes up with next.
Click to expand...
Click to collapse
No wifi-error on neofroyo with ygge-kernel？ I have tried many times. But wifi never works. Can you share your kernel to me?
http://db.tt/V7TKnyV
don't use the wifi-fix provided on neopeek. (i never did and it still worked fine; that's my old setup, i switched to midnight's kernel since then)
Thank you.
Is there anything that can make the battery last longer on Android??
While x1 on Windows can last for three days Android last only one day?
I have galaxy s since last one year and i love it... However my phone has become very slow these days.. I tried several roms and kernels.. Formatted both internal and external SD cards... But still it is very slow... I remember that I dropped it 3-4 times... Is it because of it?
Can someone suggest me please... What should I do...
Sent from my Galaxy S using Tapatalk
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
309041291a said:
Maybe over clock it ...? I thought the new ROMs would have helped. It could be the fact that your phone is older now and some internal hardware has been worn out
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
Click to expand...
Click to collapse
Can I do anything related to the hardware? I mean how can i check if it is not giving 100%?
Sent from my Galaxy S using Tapatalk
I'm no expert so I'm not sure. Best bet would be to replace the hardware which Costs a ton of money. Its better to just a get a new phone. Either that or maybe mess around with new ROMs some more. Maybe you are wiping your phone incorrectly or maybe you use it too much
Nexus S (GSM i9020a)
CM9 Nightly Kang (Build 5 of 2.1)
Eugene's Kernel (Speedy-7)
OC 1100/100 (lulzactivev2)
my suggest...
1. update your firmware to last version (2.3.6).
2. try to change kernel and custom rom.
3. maybe, with some different kernel and custom rom, you can choice the better option for your device. for example, try using kernel semaphore (gingerbread) and custom rom F1 or other.
I would be very surprised if physical trauma has simply caused a slow-down in speed. It would more likely show itself as random reboots and other more obvious symptoms.
Much like Windows, after a lot of use, it slows down - you have said that you've flashed other roms, maybe you just haven't come across a good one; there are after all a lot of different ones...
I would suggest the deodex-ed / rooted stock rom from RAMAD Gingerbread JVT. As I remember it was always quite stable and fast.
The hardware components inside a modern phone will not wear-out after a year - they are not moving parts! - when ram or a processor wears out it usually results in total system crashing not just a slow down.
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Have you ever tried Advanced task killer? Or even killed tasks?
zadusimple said:
Thank you all for your feedbacks and suggestions. I use my phone a lot. Usually i use TV out a lot as i do not have a cable connection in my hostel room. I use my phone a lot. I flashed it atleast more than 100 times. I have not seen any reboots, crashed , soft reboots etc very often. When i use MIUI rom my phone is very fast indeed however , it does not have a TV Out and therefore i have to use a stock based rom.. i will try Rammad's GB Rom as per your suggestion and will report back. As i told you that i dropped it a couple of times, is it possible that any of the Internal components have become loose?
Click to expand...
Click to collapse
Did you try the ics roms. These r pretty fast..specially team icssgs.
Sent from my GT-I9000 using Tapatalk
Try ICSSGS RC 4.2. I had the same situation as you. It was fine for one year and I was using Darky rom by that time. Suddenly I started feeling that my phone is too slow. Lot of stuck. Sometimes I had to remove battery just to restart.
Now running above ICS rom with Devil 14.2 Kernel its rocking ...
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
gezze said:
yeah I'd suggest u the advanced taskkiller too
in options you can set the auto killlevel to safe, so that it kills smth like games in the background but not important apps
since then my phone is quite fast even with stockrom
Click to expand...
Click to collapse
Yeah, and you can just use the ATK widget when you close out of something press the icon and it kills all the background apps...
I will surely try ATK and ICS roms as per your suggestions...
Sent from my Galaxy Nexus using Tapatalk
keep us updated...
Just get stock jw1, flash with reparation to wipe everything, then do a factory reset via secret dial code. Now install semaphore 2.5.0 kernel. Dl superuser to get root. Now install thunderbolt tweaks the main package and the 60lmk other addon(read thread how to) . This is the best setup i can think of in terms of speed bat life and functionality. Next step look in pikachus Android optimization thread and remove the bloatware listed there, basically remove as much bloat as possible. Enjoy ur fast phone.
Sent from my GT-I9000 using Tapatalk
Perhaps you should try the ICSSGS RC4.2 with Devil 14.2 LED VC Kernel. I'm on it and its awesome, my phone lags no more and I'm using it for my primary phone.
Sent from my Galaxy S using XDA Premium
First of all, I expect that mrs. reinbeau doesn't close this post, I feel it necessary in order to solve the main problem of my ROM.
This post is intended to all of you that have the problems so called SoD (Screen of Death), when the phone sleeps but don't awake... and the frozen screen problems too...
It's a new ROM progressively created from scratch in order to determine where is the problem.
Please, use it and comment here if the SoD issues are gone or remains; everything you want to say but ONLY RELATED TO THIS PROBLEM.
The instructions are easy:
- If you come from Test 2, or Test 2.1, simply flash Zeus v5 Lite over it. It won't wipe your data.
- Otherwise, make a wipe data / factory reset before flashing Zeus v5 Lite
- AFTER INSTALL IT, IN BOTH CASES, FORMAT /CACHE (--> mounts and storage --> format /cache).
- Once you have Zeus v5 lite, directly flash Zeus v5.03 over it.
- Zeus Test 2 (full wipe, complete ROM): d7fc02c423df42ecbdc4a9a2a0f7255c - Mirror
- Zeus Test 2.1 (dalvik and cache wipe, complete ROM): a3c20899db2d59e09fab60dd6aeb6094 - Mirror
- Zeus v5 Lite (dalvik and cache wipe, complete ROM): c55155a8aac4e5300b8239c08e739bd6 - Mirror
- Zeus v5.01 Lite (dalvik and cache wipe, update to Zeus v5 lite): 9a2907c9aec64857495fec093495afd1 - Mirror
- Zeus v5.02 Lite (dalvik and cache wipe, update to Zeus v5 lite): eee81e29f285d261fe442a370bb4dffb - Mirror
- Zeus v5.03 Lite (dalvik and cache wipe, update to Zeus v5 lite): f52fc7b9c2534da91c09f937c13b13f5 - Mirror
Changelog:
Test 2: Initial base ROM lightwighted, with original kernel and some opts.
Test 2.1: Fully themed Test 2, additional cleaning and some opts.
Zeus 5 lite: Prerelease, test it please... It has a lite zeus script, txpower, some opts, new Google Play Store...
Zeus 5.01 lite: To flash over Zeus 5 lite. Stock kernel recompiled with Linaro (unaltered, with stock configuration), with a new runtime parameter to enable/disable led dimming (thanks to sergey1369) and with led supply current reduced in a 20% to save battery. Updated zeus script with options to enable/disable led dimming and to change lockscreen. Fixes symlink to 'cp' busybox command.
Zeus 5.02 lite: To flash over Zeus 5 or 5.01 lite. Same features as 5.01 + cache again with ext4, new optimized mount options and fixed the auto enable/disable dimming at boot.
Zeus 5.03 lite: To flash over Zeus 5, 5.01 or 5.02 lite. Same features as 5.02 + new governors(interactiveX, Smartass2 and OndemandX[default]) + deadline + total control of the leds (high intensity, low intensity, enable/disable dim, timer) + txpower stock by default (touch it if you want) + runtime enable/disable fsync() enabled by default + upgraded zeus script... look into it!
Regards and thanks!
About 12 hours with your fix and everything is OK. I have v3.2b.
Pr3dator? said:
Is there a way to fix this on cyanogenmod
Envoyé depuis mon LG-P970 avec Tapatalk
Click to expand...
Click to collapse
What do you understand with ONLY RELATED TO THIS PROBLEM?
pk76 said:
About 12 hours with your fix and everything is OK. I have v3.2b.
Click to expand...
Click to collapse
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
tsakaji30 said:
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
Click to expand...
Click to collapse
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
And no, there's no strange changes to kernel to boost anything that can harm your phone.
Regards.
Huexxx said:
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
Click to expand...
Click to collapse
Ok, I'm going to try this again from scratch.
Another important thing: I was having the same problem since V2, then I flashed V3 and it was gone by 2 or 3 days, then, yesterday my phone restarts itself and after that is a chaos hehehe
If is not something related to the graphics, then maybe is something related with the way your version commit data in the memory and maybe there is a data corruption that makes the phone behave weirdly.
Anyway, thanks a lot for your big effort, I regained the thrust in my phone after testing your zeus rom (i was just to sell the black and buy a Nexus hehehe).
Regards!
Thread cleaned
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Huexxx said:
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Click to expand...
Click to collapse
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
reinbeau said:
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Click to expand...
Click to collapse
Sorry!!!!!!!!
pk76 said:
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
Click to expand...
Click to collapse
Everyone can do what he want! The "old" fix was a quick attempt to fix the problem. While you don't have the problem, don't try this stuff becuase it's intented to catch the problem; no problem -> no catch...
Someone said that with the "old" fix the problem persists, so I have created this post to progressively approach the problem to know where is it, and then erradicate it!
- If people try this fix and the problem persists, it will be at the ROM itself, not in the kernel/boot.img/build.prop -> then we'll try to find it on the ROM.
- If people try the fix and the problem is gone, the problem is at my latest kernel/boot.img/build.prop, so I'll change progressively that stuff until we get the error again...
There's no other way IMHO.
Regards.
already activated fsyn and flahs ur fix, I ll give my feedback in a few hours, just let my try...
With my fix (THIS FIX, ON FIRST POST) there's no possibility of deactivate fsync because it's a diana kernel feature and wiht my fix you will have the stock kernel...
Thanks!
First of all, I'm not using this rom, I'm using cm7 temasek's build BUT I think somehow is related because this "SoD" is happening at the new builds...
And I wonder why? well I don't know but, it may be something with the rom itself?
Zeus is "official" and cm7 is "mod" but they're both based on gingerbread so there must be some connection.
I'm not trying to complicate things but trying to help, because this is not an isolated issue from zeus, this is present at cm7 new builds too.
Sorry but is not the same IMHO...
- CM7 are constantly changing and for whatever reason the most recent builds have this problem. So, different builds...
- my rom comes from stock rom (that doesn't have the problem, or that's what we hope...) and in a certain moment with some modification (of my own) the problem has emerged, WITH THE SAME BUILD.
When I find my problem, I hope it can allow cm7 people to fix the problem, but I'm afraid there are a lot of reasons why it can happen.
This thread is to test my rom with different things trying to find the bad change made to my rom, not a thread to discuss about Screen of Death.
Thanks anyway.
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
I also never faced this SoD with your ROM (3.0n) and I'm using it for a while now. I skiped 3.1 patch and installed 3.2 yesterday and no SoD. But with cm7 I had this once don't know what version.
On the other hand a colleague at work have this issue with 3.1n a few days after install. I installed the 3.2n and we'll see.
yesterday I got 2 frozeen displays and have to remove battery,
Today (like about 5 hours ago) flash this fix and until now I dont have that problem at all... I just want to give my feedback, but I ll post again 5 hours later to say if donst get the problem again.
Sry about my pretty bad english.
Hackpb said:
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
Click to expand...
Click to collapse
I've faced only one SoD, thats the reason i need people that have experimented more sods because their way of use the phone.
Sent from my LG-P970 using XDA App
Does anyone know if the app "Captivate Keep Alive" is compatible with ICS?
I had been using it, but since I upgraded to ICS, it launches and shows the icon in the status bar, but only shows it initially in running services, then still in status bar, but soon after doesn't show it in running services, no battery drain (apparently it's stopped) and won't close, have to force stop to get it out of the status bar.
Tried to find on the Dev site, App Brain, etc. any documentation, but can't find anything about compatibility with ICS
Unfortunately my phone suffers the random shut downs, especially at high battery levels, when idle.
Thanks
Ive heard of it not working before with ICS based ROMS. But specifically im talking about the Team ICSSGS ROM. So first, you need to tell us what kernel you are running and what ROM. Because I switched to the Glitch new build 2 days ago and have yet to suffer a random shutdown or charge death which I got almost daily with the old build. We will see if this lasts though.
capocaccia said:
Ive heard of it not working before with ICS based ROMS. But specifically im talking about the Team ICSSGS ROM. So first, you need to tell us what kernel you are running and what ROM. Because I switched to the Glitch new build 2 days ago and have yet to suffer a random shutdown or charge death which I got almost daily with the old build. We will see if this lasts though.
Click to expand...
Click to collapse
Thanks,
running Doc's Master ICS V5 with the included kernel Glitch V14-B5 Kernel
I also wasn't having any shutdowns, and thought maybe it was solved with this ROM/kernel, but then had an overnight shutdown about a week ago, but still overall probably better, because when I get up in the morning and see that captivate Keep Alive stopped, and battery is at over 80% and didn't shut down, so looking better, except that one shutdown.
Ok, B5 just had a new release a few days ago but for some reason the dev didnt change the title or update the thread. He just made a post about it. I just want to be sure, are you running the kernel I have linked in this post? It was just posted 2 days ago.
http://forum.xda-developers.com/showpost.php?p=23665451&postcount=965
Haven't updated to the most recent version, still the version that came with the ROM, which I downloaded maybe 2 weeks ago. Didn't see the kernel was updated, now wondering if I should consider updating the kernel to the newer version, notice he indicates Nandroid backup should work, which is nice.
Edit: not clear if the other version is the right one for my ROM, maybe should stick with the version I have.
Edit 2: I guess that's the only glitch kernel, as you mentioned he hasn't updated the title/name inn a while (on my phone the version from 2 weeks ago shows V5)
M973 said:
Haven't updated to the most recent version, still the version that came with the ROM, which I downloaded maybe 2 weeks ago. Didn't see the kernel was updated, now wondering if I should consider updating the kernel to the newer version, notice he indicates Nandroid backup should work, which is nice.
Click to expand...
Click to collapse
I would. Thats the kernel I am running and have found it more stable than the older release. Its a simple download and flash through CWM.
EDIT: If you are currently running ICY Glitch, then an update will not effect anything. If you are currently running another kernel then you will need to check first. Post in the Q and A for your ROM.
capocaccia said:
I would. Thats the kernel I am running and have found it more stable than the older release. Its a simple download and flash through CWM.
EDIT: If you are currently running ICY Glitch, then an update will not effect anything. If you are currently running another kernel then you will need to check first. Post in the Q and A for your ROM.
Click to expand...
Click to collapse
Thanks, I'm seeing that, just not as clear without the updates to the version number, etc. Will do.
Hi,
Anyone else having problem with hot reboots? Had texas, bcm and aopk on my phone but never had a solid running system.
Right now I've got aokp which only gives me one reboot right after start.
What is your experience?
I have been running BCM for days now, without any issues. Check your partition formats, start with clean flash and see what happens.
Formated the old sd card via gparted. For the new one I used 4ext recovery...
And I always make a full wipe before I flash a new rom.
happyass**** said:
Hi,
Anyone else having problem with hot reboots? Had texas, bcm and aopk on my phone but never had a solid running system.
Right now I've got aokp which only gives me one reboot right after start.
What is your experience?
Click to expand...
Click to collapse
Which version of AOKP are you using? May 30? It seems that the dev has confirmed the software and hardware problems. He recommends to use 1 or 2 version back. I am using May 27 version and didn't have hot reboot issues often. It rebooted sometimes.
I got the same issue with setcpu v2.4 running with these ICS rom's. I upgraded setcpu then things are OK now.
Sent from my Nexus One using XDA
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
taodan said:
Which version of AOKP are you using? May 30? It seems that the dev has confirmed the software and hardware problems. He recommends to use 1 or 2 version back. I am using May 27 version and didn't have hot reboot issues often. It rebooted sometimes.
Click to expand...
Click to collapse
I also use the May 27th version.
In the meantime I tried every other ICS Rom once more (texas, BCM and Miui V4). Also flashed those roms with the kernel aopk uses.
So far aokp is the best one.
Hopefully aokp will be continued soon.
@phhuang
Good idea. Gonna try setcpu.
What are your settings?
I had the same reboot problems you have with BCM older than 12/06/09.
Since then, no particular problem, except the governor falling back to userspace after each reboot, hence quite laggy.