Hi I´m sure most of you are aware of this problem, the unstable fps after 2.1 update I installed the dexter froyo rom hoping i would finally be able to fix this issue but to my surprise the problem remains.
I´m aware that changing the governor on set cpu from on demand to performance it helps a bit but i still see the stuttering playing mostly emulators !
I´m running at 800 mhz and I still have drops from 60 to 40 fps constantly.
Is there a fix for this that i´m not aware of ?
Pls help !
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
yeah i was aware of that post and the being investigated situation by motorola ..... motorola europe does a lot of research but real work not really ...
the new update of 2.1 that is currently rolling out fixes this problem??????
kniffo80 said:
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
Click to expand...
Click to collapse
Thats because we can only use the 2.1 Kernel at the moment.
I´d rather use the 2.01 since i could play most emulators perfect ....
Is there any way to downgrade it using open recovery ?
mousiope said:
I´d rather use the 2.01 since i could play most emulators perfect ....
Is there any way to downgrade it using open recovery ?
Click to expand...
Click to collapse
you may downgrade your phone to 2.0.1 flashing a full sbf file from here (e.g.)
http://and-developers.com/sbf:milestone
remember to use a FULL sbf not a service sbf.
I tried it yesterday and my 2.0.1 milestone gives me at stock 60 FPS with fps2d!!! dexter's frenzy is not fixing this problem
kniffo80 said:
Motorola is aware of the problem. I think, it's a kernel related thing, but i don't know exactly. The fact, that the framerate dropped, is known so far:
There's also a thread at motorola discussion boards:
http://community.developer.motorola...-Milestone-2-1BUG-major-2D-slowdown/td-p/5719
So, the thing is known. And it was promised to be fixed with froyo. but it seems not to be fixed i don't get any solution for now. i'm searching a few days also now.
Click to expand...
Click to collapse
bad link? (10 chars)
The link is not broken, works fine for me
Another link to Google Code: http://code.google.com/p/android/issues/detail?id=7520 i've bumped the thread. perhaps, someone can tell us, what has been changed to fix the 30 FPS issue and i HOPE this is not a motorola kernel fix (some module changes) - cause 2.0.1 and 2.1 use both 2.6.29 kernel.
EDIT: @silico: no, it should not pend on the kernel. i just flashed my milestone with 2.0.1 and after flashing that fresh full sbf (with 2.0.1 kernel) i restored nandroid frenzy v 0.5 (which is not changing the kernel at all) and ran into the same problem: after restoring dexter's frenzy, the framerate dropped again to 30 FPS on stock clock!
here is a patch library which might work fine on regular stock firmwares too, but its not tested much..but results are 60fps+ now even on 550mhz
update-script fixed
kniffo80 said:
The link is not broken, works fine for me
Another link to Google Code: http://code.google.com/p/android/issues/detail?id=7520 i've bumped the thread. perhaps, someone can tell us, what has been changed to fix the 30 FPS issue and i HOPE this is not a motorola kernel fix (some module changes) - cause 2.0.1 and 2.1 use both 2.6.29 kernel.
They use the same kernel ? Where did you saw that?
I´m using the GOt´s modified sbf for uk and the problem remains !
If I downgrade the sbf to 2.01 i gain the stability for the 60 fps but what are the disavantages of using 2.01 ?
And you also say after using 2.01 sbf and recovering moto frenzy image you went back to 30 fps, so where is the problem in the kernel or in the image ?????
If you are using motofrenzy image now if you downgrade to 2.01 after the image is already in use the problem remains???
Thanks dexter for the reply ! Are u gonna include that on your image soon?
How do I apply it? to a stock image can anyone help me?
Click to expand...
Click to collapse
mousiope said:
Thanks dexter for the reply ! Are u gonna include that on your image soon?
How do I apply it? to a stock image can anyone help me?
Click to expand...
Click to collapse
just use "apply update" or you copy the lib yourself directly into the /system/lib/hw folder manually.. (gralloc.omap3.so is the name of the file)
the first update-nosign.zip was messed up, please make sure you have the last one i uploaded now..
Dexter_nlb said:
just use "apply update" or you copy the lib yourself directly into the /system/lib/hw folder manually.. (gralloc.omap3.so is the name of the file)
the first update-nosign.zip was messed up, please make sure you have the last one i uploaded now..
Click to expand...
Click to collapse
I´ve just applied it it didnt´t worked.
the problem persists and it messed up my graphics !
I´ve just loaded your image and applied this update it messed up my graphics exactly the same way !!!
Its like i´m seeing artifacts.
I copied it manually to my phone with 2.1u1 and it fixed the 2d slowdown problem but it does mess up the main GUI, the emulated games run perfect though, only emulator menus have the same problems the main GUI has, ingame they are perfect!
Super smooth like in 2.0.1 but able to overclock
okay. the lib from dexter is from droid 2 and it seems, there are some sync problems. this causes the glitches on the screen. yes, 60FPS are back, but which price?
so i started a thread in cyanogen forum, asking for the libs from CM 6 RC3 to be used to crack that 30 FPS cap.
I tried the libs from the CM6RC3 and that does not solve the issue
Anyway lets wait and see what happens.
We are a bit closer already, I can play my emulators at full speed
Renegade_Rulez said:
I tried the libs from the CM6RC3 and that does not solve the issue
Anyway lets wait and see what happens.
We are a bit closer already, I can play my emulators at full speed
Click to expand...
Click to collapse
which libs did you try? i already tried only changing gralloc.omap3.so, but same result, as yours. i wonder, how cyanogen fixed that cap ...
I tried gralloc.omap3.so and gralloc.default.so but that got me the low fp/s again...
Strange that they fixed it in another way then...
Would it be possible to use gralloc.omap3.so from a milestone 2.01 rom. The bug was also pressent in 2.0. But they fixed it in 2,01. Maybe they just accidently used the bad libs again in 2.1.
If i use the files from my 2.0.1 release it wont boot anymore...
Renegade_Rulez said:
If i use the files from my 2.0.1 release it wont boot anymore...
Click to expand...
Click to collapse
same here. also tried other libs together (from 2.0.1), as all under /system/libs/hw and
- libpixelflinger.so
- libpvrANDROID_WSEGL.so
- libskia.so
- libskiagl.so
- libsurfaceflinger.so
and from egl:
- libGLES_android.so
same: stuck at motorola bootlogo
done for today ... too much nandroid restores
Related
initial from story DROID LIFE.com thanks kellex
forgot to mention this is for 2.2
http://rootzwiki.com/
So now that w ehave the 2.2 SBF, is it pretty much safe for us on 2.2 OTA to use the custom ROM's on here (w/ Koush's bootstrap)?
OP, actually, it was RELEASED in this very foum. MODs killed it this morning. Guess they were afraid of the C & D. If you were on here about midnight EST last night..... you had it before it even hit the tor's
iamrobk said:
So now that w ehave the 2.2 SBF, is it pretty much safe for us on 2.2 OTA to use the custom ROM's on here (w/ Koush's bootstrap)?
Click to expand...
Click to collapse
I have, and i had a successfull re flash with system sbf
get it while you can
catalystsupreme2 said:
I have, and i had a successfull re flash with system sbf
get it why you can
Click to expand...
Click to collapse
Cool, thanks. And yeah I downloaded it earlier just to have it (did the same thing with the 2.1 SBF, so i should be pretty set).
so will this allow a direct upgrade from the 2.2 leak to the 2.2 official?
I'm still seeding if anyone cares.
It will"flash" your phone to the ota with the new kernel, baseband etc. So yes to answer ur question. This is the same utility file used by "technicians" in store to recover or reset devices. Our equivalent of a ruu I guess. Be sure you have the latest rds lite 4.8 I think. Also make sure ur drivers are up to date.
Sent from my DROIDX using XDA App
Gimpeh said:
I'm still seeding if anyone cares.
Click to expand...
Click to collapse
Where are you seeding? which torrent
I'll reply to your message when i get home. Out and about at the moment.
It works
I used this earlier today after I started getting some force closes when I used the battery manager and other odd behavior after I rooted. Once it did what it needed to I did a factory reset and now I'm back to factory and the battery stats fc issue is fixed.
DroidEris1981 said:
I used this earlier today after I started getting some force closes when I used the battery manager and other odd behavior after I rooted. Once it did what it needed to I did a factory reset and now I'm back to factory and the battery stats fc issue is fixed.
Click to expand...
Click to collapse
I would give the Battery Stats FC issue some time before you say it's fixed. It's a known issue with the OTA and Moto acknowledged it so sorry to burst your bubble, but it'll come back. It's off and on and seems random.
Nice leak. Now Dx development can proceed in earnest. I needed this badly. Seeding now...
Sleuth255 said:
Nice leak. Now Dx development can proceed in earnest. I needed this badly. Seeding now...
Click to expand...
Click to collapse
I've seen some of your work with the WinMo... glad to have you in the Android world!
DroidEris1981 said:
I used this earlier today after I started getting some force closes when I used the battery manager and other odd behavior after I rooted. Once it did what it needed to I did a factory reset and now I'm back to factory and the battery stats fc issue is fixed.
Click to expand...
Click to collapse
avlfive said:
I would give the Battery Stats FC issue some time before you say it's fixed. It's a known issue with the OTA and Moto acknowledged it so sorry to burst your bubble, but it'll come back. It's off and on and seems random.
Click to expand...
Click to collapse
Agree with avlfive... I can basically toggle the Battery STats FC by rebooting my phone.
Moto has acknolwedged it, like he said, and has given NO timetable on a fix. They just say it's slated for a "future release"
Mirror
In roughly 15 minutes, the sbf will be available for download at http://rdp.yagoolio.info/downloads
Mirror for Droid x sbf
http://rdp.yagoolio.info/downloads/droidx/VRZ_MB810_2.3.15_1FF_01.zip
http://rdp.yagoolio.info/downloads/droidx/rsdlite_4.8.zip
These are hosted on my dedicated server.
so mif im on 2.2 this want brick my phone correct?
this one will not brick a 2.2 phone. it will flash droid x to latest 2.2 release from moto/vzw
Dumb question...if Im already rooted then im still gonna be rooted when I install this right? Im running 2.2 of course. Version 2.3.9
EfferusIgnis 1.0
I cooked This ROM for my own usage, i personally find it adequately snappy, responsive and reliable. If tour in the uk on 3 network, like a Sense ROM then this may be for you!
A Big Thanks to:
Danne_jo - for my first cooked Rom experience on the Wildfire
Adeadrat - for my first Bloatware free Senseless Rom experience on the Wildfire
HCDR.Jacob - Awsome Kernel (CM6 Wildfire - Cant wait to see more thanks for all the hard work Jacob!!)
Dsixda & Daneshm90 - for Awsome tools, with which without I would have still been working on this Rom...
THIS ROM IS INTENDED FOR UK USE WITH THREE NETWORK (Contains 3 stuff)
Screens
Highlights
- Android 2.1 - BASE 1.16.771.3
- Kernel 2.6.29
- Rooted
- Busybox & RunParts
- Apps2SD (SDcard ext partition required -no bigger than 512Mb-)
- Wireless Tethering
- Nano Text Editor
- Bash Shell Support
- Deodexed
Installation
As with all custom ROM's Nandroid Backup first (rooted wildfire only) !!!
ClockworkMod Recovery - wipe data/factory reset before install...
ClockworkMod Recovery - install zip from sdc --> choose zip from sdc (EfferusIgnis...zip)
ClockworkMod Recovery - reboot system now
IF you would like to OC then go here:
HCDR.Jacob Flash over any ROM Awesome Kernel 4.1 - Thanks to HCDR.Jacob and ralle.gade (+any other contributers for this)
Personally I find that, as is, the ROM is responsive enough for me, solid and reliable, I have found that with setCPU running (with standard Kernel) that I get some momentairy freezes and momentairy freezes accepting calls, just so that your aware of this... with HCDR.Jaccob 4.1 Kernel I couldn't say if the same problem exists as not tested...
This ROM, as is, has no know problems (without SetCPU running)
Download
EfferusIgnis_1.0.1_(Eclair)_Three_uk_ROM
Any comments etc welcomed - If I dont post back its because I am away for the next 10 days so I will try my best to read all when back.... (20.10.2010)
CHANGE LOG
v.1.0.1
MyTouchMusic - added -
Default wallpaper - Fixed -
v.1.0
First build....
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Reserved xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Downloading now. I will give my views later. I have always wanted to have my3 stuff on Puzzle so............
The only real BIGGIE for me is I use MyTouchMusic on Puzzle such alot that it always makes me keep returning to Puzzle.
Re-download before you flash am re-upping with MyTouchMusic
adamsy said:
Re-download before you flash am re-upping with MyTouchMusic
Click to expand...
Click to collapse
Re-downloading now. Will report back in a little while.
I dunno why anyone would want to keep the 3 stuff, but each to their own.
windywoo said:
I dunno why anyone would want to keep the 3 stuff, but each to their own.
Click to expand...
Click to collapse
I didn't want all the three stuff, just wanted to be able to log in to My3 which is something you cannot do without having Planet 3 installed.
I have been running this rom since yesterday and not found any problems with it so far.
tuktukscotty said:
I didn't want all the three stuff, just wanted to be able to log in to My3 which is something you cannot do without having Planet 3 installed.
I have been running this rom since yesterday and not found any problems with it so far.
Click to expand...
Click to collapse
What about going to www.three.co.uk with wifi turned off and then clicking My 3 Account near the top right?
windywoo said:
What about going to www.three.co.uk with wifi turned off and then clicking My 3 Account near the top right?
Click to expand...
Click to collapse
There is that I suppose but it's easier if there is a direct click that you don't have to log in to each time.
tuktukscotty said:
There is that I suppose but it's easier if there is a direct click that you don't have to log in to each time.
Click to expand...
Click to collapse
Set it as a bookmark. There shouldn't be a log in if you are accessing over 3's network.
Is wireless tether not working in this ROM? Can anyone confirm? Ive tried it on 2 wildfires and multiple computers.
It seems to work, but it doesn't alert me to the connection and the computer has no internet despite the wireless connection being there.
Thanks!
dselvey said:
Is wireless tether not working in this ROM? Can anyone confirm? Ive tried it on 2 wildfires and multiple computers.
It seems to work, but it doesn't alert me to the connection and the computer has no internet despite the wireless connection being there.
Thanks!
Click to expand...
Click to collapse
I will look into this...
Is anyone interested in an option to remove 3 stuff from Rom, or at least some of it?
Sent from my HTC Wildfire using XDA App
adamsy said:
I will look into this...
Is anyone interested in an option to remove 3 stuff from Rom, or at least some of it?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
The tether issue is a kernel issue.
My kernel seems to only enable tethering in froyo as well, not eclair for some reason.
If I get time I can compile you a kernel which is completely stock but with wireless tether enabled
HCDR.Jacob said:
The tether issue is a kernel issue.
My kernel seems to only enable tethering in froyo as well, not eclair for some reason.
If I get time I can compile you a kernel which is completely stock but with wireless tether enabled
Click to expand...
Click to collapse
Thanks Jacob...
That would be great jacob, thanks!
What i would really like to see with this ROM is something very similar to the WildPuzzle Eclair 1.0.1 (this rom was missing the reboot option on the powerscreen and then reboot into recovery option) but with the 3 boot screen and maybe some of the apps and obviously android wifi tether working on one of them.
Jacob says its his kernel causing the tether issue, but im sure ive ran his kernels before on my eclair wildfire and had wifi tether working, also with the standard kernel ive not had it working recently. Wildpuzzle eclair 1.0 was the last distro i had it working on if that helps isolating the problem?
Just out of interest did front button wake work in this rom, i forgot to try it when i tried the rom.
Thanks
Wifi Tether works for me on this rom. My pc picked it up straight away and got internet page up straight from the off. I don't mess with kernels and setting cpu etc so it's not that I've done anything to make it work.
Strange, it doesn't work for me with this ROM or Wildpuzzle Eclair 1.0.1? If its not the ROM what could it be? Any ideas anyone?
dselvey said:
What i would really like to see with this ROM is something very similar to the WildPuzzle Eclair 1.0.1 (this rom was missing the reboot option on the powerscreen and then reboot into recovery option) but with the 3 boot screen and maybe some of the apps and obviously android wifi tether working on one of them.
Jacob says its his kernel causing the tether issue, but im sure ive ran his kernels before on my eclair wildfire and had wifi tether working, also with the standard kernel ive not had it working recently. Wildpuzzle eclair 1.0 was the last distro i had it working on if that helps isolating the problem?
Just out of interest did front button wake work in this rom, i forgot to try it when i tried the rom.
Thanks
Click to expand...
Click to collapse
Sure adding reboot menu is fairly straightforward thanks to the guys here at XDA... so I will add as soon as I get chance....
Prehaphs a logcat might reveal the prob?
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 all!
I'm working on a new ICS stock based ROM to follow up Zeus, but I'm encountering some problems that are stopping my work. I hope someone can help me.
As in previous ROMs, I do everything from scratch, so i don't use other compilations or kernels, so I have to do all the work from zero.
First problem: LGEIMEbin.apk... It works flawlessly on odexed rom, but it fails to work on deodexed one... Does the LG keyboard work well on V30B based DEODEXED roms? I have fixed it editing its smali code, but I think it should work 'as is' without additional modifications...
Second and HUGE problem: gmail and browser fails... I had the ROM ready to launch but gmail began to fail... You launch it well, but when you try to open a message... it takes a while thinking and the app is auto-killed. The same with browser... it tries to load home page but stucks the progress bar and then app is killed. When I reverted latest changes... the problem persisted... in the beggining it was solved with a reboot but in latest moments it failed all the time.
I've started all the work from scratch again... step by step... and the problem has appeared again... Reverting to a fully-working state is failing too and I don't know how to fix it...
Then, the questions are:
Does the LG keyboard work well on other deodexed V30B 'as is' without additional modding? What app/version are you using to deodex the rom? I'm on latest dsixda with latest smali/backsmali.
Did anybody experience problems with gmail and/or stock browser?
I'm starting to think that my ROM is entirely bad deodexed and its generating me a lot of problems.
Regards and thanks!
I am no developer but i am using tantrums rom which is deodexed and keyboard and gmail and everything is working flawlessly... may be you can ask him
Sent from my LG-P970 using xda app-developers app
hey mate , look all my roms which are based on v30b are deoxeded but if i to be true i didnt do it ,, a friend in bbs.gfan did it he's called "lim417"
,, but also there is one dev here who actually deoxeded the rom succesfully including the keyboard and all apps u mentioned ,, he is "tantrums"
,, he deoxeded all the rom with its apps succesfully ,, contact him for the best
rrgrrg said:
hey mate , look all my roms which are based on v30b are deoxeded but if i to be true i didnt do it ,, a friend in bbs.gfan did it he's called "lim417"
,, but also there is one dev here who actually deoxeded the rom succesfully including the keyboard and all apps u mentioned ,, he is "tantrums"
,, he deoxeded all the rom with its apps succesfully ,, contact him for the best
Click to expand...
Click to collapse
as far as I remember, only email app (LGEmailbin.apk) in Marvel v D that doesn't work
while keyboard, browser, and gmail works
cmiiw
Huexxx said:
Hi all!
I'm working on a new ICS stock based ROM to follow up Zeus, but I'm encountering some problems that are stopping my work. I hope someone can help me.
As in previous ROMs, I do everything from scratch, so i don't use other compilations or kernels, so I have to do all the work from zero.
First problem: LGEIMEbin.apk... It works flawlessly on odexed rom, but it fails to work on deodexed one... Does the LG keyboard work well on V30B based DEODEXED roms? I have fixed it editing its smali code, but I think it should work 'as is' without additional modifications...
Second and HUGE problem: gmail and browser fails... I had the ROM ready to launch but gmail began to fail... You launch it well, but when you try to open a message... it takes a while thinking and the app is auto-killed. The same with browser... it tries to load home page but stucks the progress bar and then app is killed. When I reverted latest changes... the problem persisted... in the beggining it was solved with a reboot but in latest moments it failed all the time.
I've started all the work from scratch again... step by step... and the problem has appeared again... Reverting to a fully-working state is failing too and I don't know how to fix it...
Then, the questions are:
Does the LG keyboard work well on other deodexed V30B 'as is' without additional modding? What app/version are you using to deodex the rom? I'm on latest dsixda with latest smali/backsmali.
Did anybody experience problems with gmail and/or stock browser?
I'm starting to think that my ROM is entirely bad deodexed and its generating me a lot of problems.
Regards and thanks!
Click to expand...
Click to collapse
Older version of smali/baksmali caused FC on Korean ICS Keyboard aswel, but your already using newest smali/baksmali?! You can try the new apktool - it uses baksmali/smali so it probably won't make a difference. (I use that mostly)
You can try and place the original ODEX files in the dalvik cache and see if the problems persists. After deodexing the generated odex files should be very similar anyway.
Don't know about the GMail and Browser. I'm on Official V30B with a few adjustments of my own.
Also on a unrelated note. The modified bootargs that the kernel boots with on V20 bootloader differs from that of the V30 bootloader. (The CRC arg doesn't get edited out on startup so that will probably stop it even if the V30 bootloader isn't locked)
xonar_ said:
Older version of smali/baksmali caused FC on Korean ICS Keyboard aswel, but your already using newest smali/baksmali?! You can try the new apktool - it uses baksmali/smali so it probably won't make a difference. (I use that mostly)
You can try and place the original ODEX files in the dalvik cache and see if the problems persists. After deodexing the generated odex files should be very similar anyway.
Don't know about the GMail and Browser. I'm on Official V30B with a few adjustments of my own.
Also on a unrelated note. The modified bootargs that the kernel boots with on V20 bootloader differs from that of the V30 bootloader. (The CRC arg doesn't get edited out on startup so that will probably stop it even if the V30 bootloader isn't locked)
Click to expand...
Click to collapse
Yeap... I'm using latest smali/baksmali... and I've sorted the keyboard problem changing a method from protected to public.
It could be a good idea to take the odex from dalvik... but I'm not fully sure that that info is the same... take into account that a odexed app needs al the odexed framework folder to deodex, so there are several dependencies between all the stuff while on a deodexed is fully independent.
Regarding gmail and browser... they aren't FCing... also, gmail is not original deodexed gmail... is the updated one... I'm afraid that everybody is using same version (becuase google play offers the update) so the problem is not in the app itself... I don't know why but the problem seems to be the same on both apps... cometimes they fail (and both apps fail) and sometimes not (both work)...
Regarding the bootloader args... that's solved... I'm pretty sure that my kernel is passing same args than stock V30B... I've checked it looking into dmesg.
Regards and thanks!
Huexxx said:
Regarding the bootloader args... that's solved... I'm pretty sure that my kernel is passing same args than stock V30B... I've checked it looking into dmesg.
Regards and thanks!
Click to expand...
Click to collapse
Good that you got it solved, sort of.
I am talking about V30B bootloader might be giving security error with CWM since CRC arg is still present after modding cmdline on boot. It really was a very unrelated note.
Now just we must wait for huexx release ^^, hopefully soon...
Sent from my LG-P970 using xda app-developers app
xonar_ said:
Good that you got it solved, sort of.
I am talking about V30B bootloader might be giving security error with CWM since CRC arg is still present after modding cmdline on boot. It really was a very unrelated note.
Click to expand...
Click to collapse
I haven't tried to use V30B bootloader... My solution uses V20S bootloader with V30B .fls, and after that flashed through CWM without problems.
I have installed stock V30B first, I've extracted the full kernel command line and I've recreated it on my kernel except the CRC part...
The problem must be in other place...
Well , i dont know how to fix things , but why does it have to be stock browser ?I bet people would be ok with Opera or Dolphin, doubt people even use stock?
d1rekt0r said:
Well , i dont know how to fix things , but why does it have to be stock browser ?I bet people would be ok with Opera or Dolphin, doubt people even use stock?
Click to expand...
Click to collapse
well Huexxx want to create a perfect rom without bugs , that's why
I have good idea for you Huexxx. Realase bugy rom with broken browser and google mail. But add dolphin and antoher mail client. Now you are thinking Im stupid. But in this way devs can easily check where is the problem and make a fix. First version of Zeus ISC must not be perfect. Just take a look on rrgrrrg Nemsis rom. On vesrion 5 get stable and without battery drain. You were helping us one year so we can help you fix yours problems. Devs will agree with me, even of that Im not a dev
1adamek said:
I have good idea for you Huexxx. Realase bugy rom with broken browser and google mail. But add dolphin and antoher mail client. Now you are thinking Im stupid. But in this way devs can easily check where is the problem and make a fix. First version of Zeus ISC must not be perfect. Just take a look on rrgrrrg Nemsis rom. On vesrion 5 get stable and without battery drain. You were helping us one year so we can help you fix yours problems. Devs will agree with me, even of that Im not a dev
Click to expand...
Click to collapse
mmm , heuxxx doesnt work that way ,, heuxxx provides roms with only his support and he cant release a buggy rom either
1adamek said:
I have good idea for you Huexxx. Realase bugy rom with broken browser and google mail. But add dolphin and antoher mail client. Now you are thinking Im stupid. But in this way devs can easily check where is the problem and make a fix. First version of Zeus ISC must not be perfect. Just take a look on rrgrrrg Nemsis rom. On vesrion 5 get stable and without battery drain. You were helping us one year so we can help you fix yours problems. Devs will agree with me, even of that Im not a dev
Click to expand...
Click to collapse
Disagree... releasing a "buggy" ROM never is a good solution or thought. Of course everyone will help as good as we can. Just another thing. My stock kernel has got some SODs and random reboots, dont really know, whats causing, so better test it for some more days. I think I ll wait with other releases, till we get a better sourcecode. Like the reboot bug when leds are off, it is not present in the official version, but in the compilable sourcecode it is... so just be careful
Sent from my LG-P970 using xda app-developers app
This time will be diffrent. How many times Huexxx asked us for help ? So Zeus ICS beta can be realased today. Everybody want help him, in this way we would like to say "Thank you".
Always fixing errors in the software is done by testers. How we can help without testing ?
1adamek said:
This time will be diffrent. How many times Huexxx asked us for help ? So Zeus ICS beta can be realased today. Everybody want help him, in this way we would like to say "Thank you".
Click to expand...
Click to collapse
+1
PS: I hate default browser (Dolphin rules!, K9 > Gmail!)
I have neither SODs not reboots, so in that way I'm satisfied.
The rom works well (there are few things in it ATM), but a gmail app failing is unaceptable from my point of view. The worse thing is that sometimes fails and sometimes not...
Stock browser is not a problem... but bath fails allways together... so the problem is related to both...
Let see what to do with it, but is very strange that my deodexed rom has FC on keyboard but tantrum's one flawlessly works... I would like to know which smali/backsmali version is using to try it, see if the keyboard is fine, and maybe gmail and browser problems are related to the same ****...
Huexxx said:
I have neither SODs not reboots, so in that way I'm satisfied.
The rom works well (there are few things in it ATM), but a gmail app failing is unaceptable from my point of view. The worse thing is that sometimes fails and sometimes not...
Stock browser is not a problem... but bath fails allways together... so the problem is related to both...
Let see what to do with it, but is very strange that my deodexed rom has FC on keyboard but tantrum's one flawlessly works... I would like to know which smali/backsmali version is using to try it, see if the keyboard is fine, and maybe gmail and browser problems are related to the same ****...
Click to expand...
Click to collapse
Huexxx try to put the browser and keyboard from tantrum's v30 and see if they're force-closing.
If they're not , maybe is a problem with your deodexed apks
Just saying
I'm sorry but I do not know where to write you
i change entropy for reduce lag and maybe reduce battery drain following this http://forum.xda-developers.com/showthread.php?t=1987032 (i make a script with personally values for read and write upthreshold) for this is helpfull this post of zeppelinrox http://forum.xda-developers.com/showpost.php?p=36231166&postcount=387
and add my operator's mnc to dcm.settings.xml (system/etc...) to make fast dormency.
Do you think is helpfull for your rom? thanks in advance
d1rekt0r said:
Well , i dont know how to fix things , but why does it have to be stock browser ?I bet people would be ok with Opera or Dolphin, doubt people even use stock?
Click to expand...
Click to collapse
but it means maybe we will have similar issues with some other apps
and i know that, huexxx will do best for himself and us
thanx huexxx
we all waiting you.