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?
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
Hi,
I'm using NovaHD, on all the versions I tested, there's always the same problem: wifi drains a lot of battery, it goes from 100% to 0 in less than a hour. The phone also lags hard when wifi is active, apps freeze sometimes.
I didn't see anyone talking about this kind of problem on the forum.
Of course I tried a full wipe, but the problem is still here...
Thanks
Which kernel are you using?
I can recommend the 3.0.36 Nova kernel Pure Edition.
With that one I get very good battery life, even with games, one hour of phoning, some internet browsing and frequent visits to gmail.
Let phone reboot a few times after install and make sure you have correct RIL. Try GetRIL or LG RIL Version.
BR
Mike
really?? i use nova hd build 16.29 for more than a month and no problem for me
have you ever tried calibrating your battery?
btw, don't bother to try older builds (16.xx, 17.xx, and 18.xx work great in my phone!)
I'm using the last "Rebuild v1.1.0", and the kernel is 3.0.33 Nova version 1.0.7, I'll try to install the Pure edition.
btw the RIL doesn't correspond to baseband so I'm installing the right one now.
dridri85 said:
I'm using the last "Rebuild v1.1.0", and the kernel is 3.0.33 Nova version 1.0.7, I'll try to install the Pure edition.
btw the RIL doesn't correspond to baseband so I'm installing the right one now.
Click to expand...
Click to collapse
I know, they dont match, according to GetRIL, but if I install matching RIL, strangely enough, I dont have any tele-connection.
I tried a few combinations, before I got the winning pair!!
BR
Mike
Thanks for helping, it seams the problem is solved.
I just changed the RIL and installed the last Nova kernel, I also removed Shazam cause it was always running in background when wifi was active.
But the last Nova kernel doesn't support OC ?!
Hello there, i have my galaxy s for two years now, i've been flashing almost every rom i found, from froyo to cm7/miui to cm9, 10, 10.1, all have been wonderful and i thank you all for this.
All the problems i ran into i solved reading through hundreeds of pages and thousands of posts without the need of asking questions, again because of this wonderfull comunity.
Cm10 is my favourite but i have a little problem with it, which appeared short after the last partition layout change. My phone is constantly and randomly freezing whenever i browse the internet (using only stock browser). By freezing i mean the image get's stuck and all buttons, exept for the capacitive which light up when i touch them. It only works to hold the power button for 8 sec for the phone to reboot. After the phone reeboots, the kernell splash screen appears il loads up then the screen hoes black, the kernell splash screen loads again then it continues normaly, it's like a double boot or something.
The problem appears only on cm10 and aokp (4.1.2), havent tried miui4.1.
I also tried stock cm10 kernel, semaphore, devil, mackay, not using oc, ov, uv, anithing special, only on ondemand and smartass v2 governators
I have to mention it happens with flash installed and also without flash, with and without big mem libraries and setting in kernel.
Some help please would pe aprecieted, because for me cm10 and derivates work best.
Thank you and sorry for my bad english
Sent from my GT-I9000 using Tapatalk 2
Ynt: I9000 freezing randomly
First off "double booting" is just because of init.d scripts you're using.Some kernel options of yours too.So that's not the problem. I'm just like you.To be honest,i WAS. I stopped using custom roms for 4 months... I'm tired,bored.... So ... Also i'm using my phone just for music,texting,calling... not games actually and stock rom with stock kernel i mean without any tweak ,it's enough for me
i'm still continuing flashing but only switching between gb roms currently i'm on JW9 (Released in Jan 14 2013 ). Custom roms always better in performance but i dont need performance... It's all about battery life and stock for me!
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Hi,
my lg p990 with the latest cm10.1 nightly is crashing all the time in a way that it doesnt work at all and drains the battery until you pull the battery out. i had this problem with cm10 and cm10.1 for ages and i dont know whats causing it. because of the way the phone crashes i dont have any logfile whatsoever. its just reallly annoying.
Any help ?
(pls dont answer like "did you turn the phone on?" or similiar non-smart questions, yes i did everything according to the "book", i also installed a lot of apps on the phone)
EntroP said:
Hi,
my lg p990 with the latest cm10.1 nightly is crashing all the time in a way that it doesnt work at all and drains the battery until you pull the battery out. i had this problem with cm10 and cm10.1 for ages and i dont know whats causing it. because of the way the phone crashes i dont have any logfile whatsoever. its just reallly annoying.
Any help ?
(pls dont answer like "did you turn the phone on?" or similiar non-smart questions, yes i did everything according to the "book", i also installed a lot of apps on the phone)
Click to expand...
Click to collapse
you used the version of the bootloader right?
humandroide said:
you used the version of the bootloader right?
Click to expand...
Click to collapse
i used the version you can download on cyanogenmod website and installed it normally via cwm (with full wipe and everything)
i never touched anything related to bootloaders (just used the standard one i guess...)
Did you use stock CM kernel?
I didn't tried the latest cm nightly, but cm kernel has a weird bug causing the CPU to stick at 1000mgz all the time.
Use some apps to see for yourself, cpu spy.
I use trikster mod app to properly set the cpu.
And I recommend avatar rom, it is like CM but has a suport/option for miui themes.
Rom is super smooth and has god memory menagement/multitasking, even the stock clock alarm hasn't failed me.
Sure it has all the known CM bugs like panorama not working, same kernel bug, ect. but it's stable.
imperator01 said:
Did you use stock CM kernel?
I didn't tried the latest cm nightly, but cm kernel has a weird bug causing the CPU to stick at 1000mgz all the time.
Use some apps to see for yourself, cpu spy.
I use trikster mod app to properly set the cpu.
And I recommend avatar rom, it is like CM but has a suport/option for miui themes.
Rom is super smooth and has god memory menagement/multitasking, even the stock clock alarm hasn't failed me.
Sure it has all the known CM bugs like panorama not working, same kernel bug, ect. but it's stable.
Click to expand...
Click to collapse
nice, i think im gonna try out the avatar rom, it really sucks having to pull the battery every 10 minutes because it crashed miserably