Hello everybody,
I'm having annoying problem with DSC
When I'm toggle mobile data,as usual I'm browsing with listening music
30mins-1hour later...my streak is freezing touching power button and screen it's not responding,I'm waiting for restart but streak not restarting after 30mins
so I remove the battery and put back again then rebooting streak,when thinking is normally back...back browsing without listening music
AND it's freezing again! everyday this problem is coming annoying
I dunno why it;s happening to me...I'm following those step for flashing stockROM and CusROM nothing is missed
I'm flashing stockROM : flash 407.pkg with rec stock 407...nothing problem
then I'm flashing DSC : Wipe data,dalvik,battery stats,fix --->> flash DSC -->> Wipe again and reboot --->> fact reset with white letters....NOTHING problem
Oh yeah,an annoying problem happening to :
stockROM 2.3.3 (407.pkg)
DSC 1.6
DSC 1.7
DSC 2.0
DSC 2.2
DSC 2.3 (it's happening to! :crying
LXdroid 0.2
Longhorn 2.9.3
On LXdroid and Longhorn...it's happening again on mobile data,but not freezing,problem like :
Longhorn :
streak is restart when using mobile data
LXdroid :
LED is blinking,some app (camera,data,music,sound) it's stopped work,power button it's not work to (so when screen off,it's won't turning on)...but touchscreen and launch other app is normally working?! (lol :silly
but on DSC...this problem make me frustated even on DSC 2.3...enabling mobile data and a few second later my streak it's freezing! I can not be patient to wait my streak restarting....be awaited 30mins it's won't restarting
I'm sure is not vault on hardware...maybe vault the ROM? or build.prop and init.postboot isn't matching? or baseband and kernel isn't matching too
A definite,someone please giving solution for my annoying problem on my streak :crying:
=============
Sorry for my bad english...I'm new on XDA
Does it happen on stock ROM?
UV deactivated?
try to flash 369 rom ... 4xx always works with bugs
Files for 369: http://rghost.net/43157067
Rocker19943 said:
try to flash 369 rom ... 4xx always works with bugs
Files for 369: http://rghost.net/43157067
Click to expand...
Click to collapse
369 rom? froyo?
no...i more comfortable with gingerbread
If you're getting an error on all listed ROMs then apparently it's the hardware problem.
zane19775 said:
369 rom? froyo?
no...i more comfortable with gingerbread
Click to expand...
Click to collapse
It's able to run Gingerbread, im using it with DSC 2.3
Rocker19943 said:
It's able to run Gingerbread, im using it with DSC 2.3
Click to expand...
Click to collapse
oh I suppose to be flashing the 369 ROM to
ok i try it...hopefully can be resolved
-----------------
not solved
completed booting to homescreen...streak is restarting back
_n0p_ said:
If you're getting an error on all listed ROMs then apparently it's the hardware problem.
Click to expand...
Click to collapse
I don't think so,n0p it just happening on mobile data
maybe i must check back the baseband and kernel version
zane19775 said:
oh I suppose to be flashing the 369 ROM to
ok i try it...hopefully can be resolved
-----------------
not solved
completed booting to homescreen...streak is restarting back
I don't think so,n0p it just happening on mobile data
maybe i must check back the baseband and kernel version
Click to expand...
Click to collapse
what the hell... mhm seems nop is right, well it should work correct on 369 baseband
I have had several different flashing all listed ROM's
and it seems the problem lies in the kernel
Phoenix Kernel u18 & u30 for CM7 make my streak freeze (on LH 2.9.3 & Lxdroid 0.2)
Default kernel from LH 2.9.3 and Lxdroid 0.2 make my streak random reboot
DSC 2.3 (and older version) default kernel make my streak freeze,when i try Phoenix kernel u10,my streak is random reboot...but not as bad LH 2.9.3 & Lxdroid 0.2
so...is there a new kernel for streak 5
UPDATE :
maybe n0p right
someone tell me that i must changed new Internal Memory because my internal memory have many cache (total cache = 265mb )
now HOW TO DO THAT???
someone please help me :crying:
zane19775 said:
Hello everybody,
I'm having annoying problem with DSC
When I'm toggle mobile data,as usual I'm browsing with listening music
30mins-1hour later...my streak is freezing touching power button and screen it's not responding,I'm waiting for restart but streak not restarting after 30mins
so I remove the battery and put back again then rebooting streak,when thinking is normally back...back browsing without listening music
AND it's freezing again! everyday this problem is coming annoying
I dunno why it;s happening to me...I'm following those step for flashing stockROM and CusROM nothing is missed
I'm flashing stockROM : flash 407.pkg with rec stock 407...nothing problem
then I'm flashing DSC : Wipe data,dalvik,battery stats,fix --->> flash DSC -->> Wipe again and reboot --->> fact reset with white letters....NOTHING problem
Oh yeah,an annoying problem happening to :
stockROM 2.3.3 (407.pkg)
DSC 1.6
DSC 1.7
DSC 2.0
DSC 2.2
DSC 2.3 (it's happening to! :crying
LXdroid 0.2
Longhorn 2.9.3
On LXdroid and Longhorn...it's happening again on mobile data,but not freezing,problem like :
Longhorn :
streak is restart when using mobile data
LXdroid :
LED is blinking,some app (camera,data,music,sound) it's stopped work,power button it's not work to (so when screen off,it's won't turning on)...but touchscreen and launch other app is normally working?! (lol :silly
but on DSC...this problem make me frustated even on DSC 2.3...enabling mobile data and a few second later my streak it's freezing! I can not be patient to wait my streak restarting....be awaited 30mins it's won't restarting
I'm sure is not vault on hardware...maybe vault the ROM? or build.prop and init.postboot isn't matching? or baseband and kernel isn't matching too
A definite,someone please giving solution for my annoying problem on my streak :crying:
=============
Sorry for my bad english...I'm new on XDA
Click to expand...
Click to collapse
Hi,
I have similar rebooting issue with my gf's streak 5. It keeps rebooting while she is on candy crush game or any other games. It reboots more frequently while playing games than doing other task like music or video streaming via dlna etc.
It is on
ROM: LXDroid ROM 0.2
Kernel: DSC 2.6.35.14-DSC-Team-Phoenix
Baseband: GAUSB1A132013-EU
Android 2.3.7
I am not sure what is the exact problem. I am from Singapore, could it be due to the baseband version that i am using that causing these random reboots?
zane19775 said:
Hello everybody,
I'm having annoying problem with DSC
When I'm toggle mobile data,as usual I'm browsing with listening music
30mins-1hour later...my streak is freezing touching power button and screen it's not responding,I'm waiting for restart but streak not restarting after 30mins
so I remove the battery and put back again then rebooting streak,when thinking is normally back...back browsing without listening music
AND it's freezing again! everyday this problem is coming annoying
I dunno why it;s happening to me...I'm following those step for flashing stockROM and CusROM nothing is missed
I'm flashing stockROM : flash 407.pkg with rec stock 407...nothing problem
then I'm flashing DSC : Wipe data,dalvik,battery stats,fix --->> flash DSC -->> Wipe again and reboot --->> fact reset with white letters....NOTHING problem
Oh yeah,an annoying problem happening to :
stockROM 2.3.3 (407.pkg)
DSC 1.6
DSC 1.7
DSC 2.0
DSC 2.2
DSC 2.3 (it's happening to! :crying
LXdroid 0.2
Longhorn 2.9.3
On LXdroid and Longhorn...it's happening again on mobile data,but not freezing,problem like :
Longhorn :
streak is restart when using mobile data
LXdroid :
LED is blinking,some app (camera,data,music,sound) it's stopped work,power button it's not work to (so when screen off,it's won't turning on)...but touchscreen and launch other app is normally working?! (lol :silly
but on DSC...this problem make me frustated even on DSC 2.3...enabling mobile data and a few second later my streak it's freezing! I can not be patient to wait my streak restarting....be awaited 30mins it's won't restarting
I'm sure is not vault on hardware...maybe vault the ROM? or build.prop and init.postboot isn't matching? or baseband and kernel isn't matching too
A definite,someone please giving solution for my annoying problem on my streak :crying:
=============
Sorry for my bad english...I'm new on XDA
Click to expand...
Click to collapse
I managed to resolve mine by using the DSC_flashme2.zip which flashes my baseband as well. You might wanna try that or try using 366B baseband. I have the tutorial shared on my blog post - link in my signature.
cripperz said:
I managed to resolve mine by using the DSC_flashme2.zip which flashes my baseband as well. You might wanna try that or try using 366B baseband. I have the tutorial shared on my blog post - link in my signature.
Click to expand...
Click to collapse
btw is working for another cusrom like Longhorn,LXdroid,or PCM7?
or just flash 366BB
zane19775 said:
btw is working for another cusrom like Longhorn,LXdroid,or PCM7?
or just flash 366BB
Click to expand...
Click to collapse
+1
Related
Thank you Trip for this wonderful rom and Z&J for the solution (I learn and pick up a lot from their roms)
I really love this rom and I hope I can help a little to make it better
J has released CM7 v14 alpha using custom kernel. Since it's still using 2.29 kernel, I tried it on MIUI and it works great
I modify TripNMiui's chargemon to make it dual boot for all miui users to play with
- This rom is still in alpha stage so do it at your own risk
- Your baseband must be 52 or the phone may reboot and back to stock kernel
- You need to know how to use adb shell or terminal emulator or gscript lite to do it
flash with xRecovery:
http://www.multiupload.com/V70JQ92E1K
The phone will always boot the stock kernel. To boot into custom kernel, do the following using adb:
Code:
adb shell
touch /data/local/tmp/kexecboot
reboot
To update future kernel, just copy the files to /system/kernel folder using root explorer and change permission.
Not working:
- Wifi
- Bluetooth
- GPS (google maps work with 3G)
- usb mount
Working: everything else
CPU is overclocked so it should be 10% faster
Screen may take a while (1-2 sec more) to wake up from sleep mode
All credits to Jerpelea
Confused?
Why would you want your stock system to have the following unavailable..
Not working:
- Wifi
- Bluetooth
- GPS (google maps work with 3G)
- usb mount
BackOrLay said:
Confused?
Why would you want your stock system to have the following unavailable..
Not working:
- Wifi
- Bluetooth
- GPS (google maps work with 3G)
- usb mount
Click to expand...
Click to collapse
well it's just to test the new kernel, that's why he made it a dual boot
I tried Z's first kernel on eternity rom when it was first released, when u flashed the kernel it stayed until you flashed something else or restored a back up, wasnt an issue at all, ran it two days n had no issues!!! Can this kernel be set up the same without a dual boot??
Sent from my X10i TripNMiUI using XDA Premium App
cjsabaki said:
I tried Z's first kernel on eternity rom when it was first released, when u flashed the kernel it stayed until you flashed something else or restored a back up, wasnt an issue at all, ran it two days n had no issues!!! Can this kernel be set up the same without a dual boot??
Sent from my X10i TripNMiUI using XDA Premium App
Click to expand...
Click to collapse
Yes you can change the chargemon script to boot direct to custom kernel. But I guess most people would prefer dual boot as this is still in alpha stage.
Sent from my X10i TripNMiUI using XDA App
True, but if you flash a rom or restore a back up, you move back to the stock kernel. Just wondering, great work by the way!! Thank you!!!
Sent from my X10i TripNMiUI using XDA Premium App
Works like a charm! First boot gave WLOD but I tried again and I got the green light. Great work, thank you!
Sent from my X10i TripNMiUI using Tapatalk
cobrato said:
Yes you can change the chargemon script to boot direct to custom kernel. But I guess most people would prefer dual boot as this is still in alpha stage.
Sent from my X10i TripNMiUI using XDA App
Click to expand...
Click to collapse
Could you also include the chargemon script to boot the custom kernel as the primary? My phone has had a few reboots, as soon as it has rebooted I have to re-apply the kernel.
sry if i upset someone with this...is the fps limit removed in this costum kernel...and 16 milion color enabled?
i found the answer..thx anyway
I think 65536 colors issue are hardware related, there is no software to fix it
JahmanSoldat said:
I think 65536 colors issue are hardware related, there is no software to fix it
Click to expand...
Click to collapse
no it is fixable.... Hence why sony said they would provide it in an update.
sorry for a dummy question.
what should i enter in the gscript?
i mostly rely on adb shell in pc.
tck9223 said:
sorry for a dummy question.
what should i enter in the gscript?
i mostly rely on adb shell in pc.
Click to expand...
Click to collapse
same command except the 1st line "adb shell"
Sorry for the dumb question, with the dual boot you still need to be on bband 52 or does the patch wotk?? Trip is working on a new miui version with the kernel too, trying to head off sum questions before they happen.
From what I have read n used, I know 52 is the only band that fits the kernel n has radio, haven't heard if the bband patch works on this or not.
Best regards,
Chris
Sent from my X10i TripNMiUI using XDA Premium App
cjsabaki said:
Sorry for the dumb question, with the dual boot you still need to be on bband 52 or does the patch wotk?? Trip is working on a new miui version with the kernel too, trying to head off sum questions before they happen.
From what I have read n used, I know 52 is the only band that fits the kernel n has radio, haven't heard if the bband patch works on this or not.
Best regards,
Chris
Sent from my X10i TripNMiUI using XDA Premium App
Click to expand...
Click to collapse
Have to be on 52
Sent from my X10i mixedMiUI using XDA App
Hello everybody, after the installation of the ROM tw008 and custom kernel 3.60 photos does not register and video does not work , somebody would have a solution?
I test all the goro's kernel and its always the same problem . Please help me!!
vinss68 said:
I test all the goro's kernel and its always the same problem . Please help me!!
Click to expand...
Click to collapse
I really want to help but unfortunately i don't know what to help you on:
But:
1: Did you install the ROM/kernel properly?
2: Did you try re-installing?
3: Did you try flashing stock firmware than Wolfbreak's ROM.
4. Did it work on stock kernel?
5. DID YOU MAKE SURE YOU DOWNLOADED THE RIGHT 3.60 KERNEL BECAUSE GORO PUT THE WRONG LINK? (oops caps)
Download the goro kernel again and flash it HERE
Hope this helps
Hello thank you for your reponse, indeed I tried some thing, and with the good kernel .
I have try:
- to make a fresh instalation of bb.67 and of the ROM tw008, then of the custom kernel 360 (by trying all the camera resolution, and play on frequence cpu, anything has to make its not working). I have not try to make a fresh installation of firmware via SEUS (I try it now!!)
-Camera is completely functional with the stock kernel , with z's custom kernel (22,23,05) and with custom kernel 3.47 when i was on tw7 bb52, but I prefere the ck 360 for the underclock and bb.67
- with and without the theme which I use
And camera make always her tantrums
Well I try the fraiche installation firmware and I informed
Works fine for me and everyone else using it...
Must be something you're doing
Just for information if it can help to resolve the problem, when I takes a photo the image gallery makes an black screen and when I want to pass in video mode the application makes a sudden closure
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
vinss68 said:
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
Click to expand...
Click to collapse
you might be flashing the wrong version of the kernel for your rom....
it's strange because all working fine, just this problem with camera . i trying to reorganize my sd card she's in a mess... maybe it's the cause of my problem.
some opinion?
I don't think its related to the rom or custom kernel. I've had this problem on some of the custom roms I've tried. What ultimately fixed it for me is by formatting the sd card so make a backup of your entire sd card then format it.
Sent from my X10x using XDA App
Good news,
my problem is resolved. Yesterday evening I completely cleaned my card sd then I left the telephone have it reconfiguré. I remake fresh installation rom tw008 and of the custom kernel 360 and hop all work fine. I think that the problem came because I tested several applications camera,background which created several files for photos,images, because which never clean .i am finally going to be able to take advantage of quite its hey hey.
Thx all to be interested in you has my case and sorry for my bad english
Hi, I recently installed CM7 Rom with BB 54 which is packed on the same zip and is working great besides know issues as camcorder and cammera itself and a couple of things...
For example:
- Im having issues with google googles... if I want to take a pic the image will be all distortionated...
- Cant use the dots at the bottom (right and left) to move arround my "desktop" cuz AWD loader will crash.
Well main issue Is the GPS here... I cant make t work. I have radio ok, Wifi ok, etc. but google earth is taking forever to find me...
I have tryed some patch's that I found crawling on the forums and the CM7 thread itself but im not able to find answers so far... is it possible to have CM7 + BB 67?
Can anyone lead me to the right forum / answer?
P.D. Yes... i have searched in these forums / yes I have used google B4 posting this ^^
are you also using a diffrent custom kernel since the default one is made for cm7 is baseband 52>
Sent from my X10i using XDA App
rtblittlebrown said:
are you also using a diffrent custom kernel since the default one is made for cm7 is baseband 52>
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Im a douche sometimes... I forgot to post that info, here it is:
- Baseband : 2.0.52
- Kernel : 2.6.29-zdzihu-mod3.60 [email protected]#1
- Mod: CyanogenMod-7.0.3-X10-J02
- Comp: GRI40
-------------------------------------------------------------------------
Yeah, I have tryed Freekernel and thanks to your question im going to try Zkernel right now... I'll let ya know what happend ^^
At the end I just was ofuscated due the constant failure and the new kernel & BB are working like a charm, GPS troubles are solved now..
Now im having some other issues LMFAO... phone is constantly rebooting and such... im going to keep trying. I can see the light now xD
thanks rtblittlebrown
Hi.
I have just installed MiniCM6 on my X10 Mini and I have everything working great. I have updated Google Maps to the latest version (5.11) from the market, and since I have a problem with Google Navigation : navigation does not re-route and map underneath route stays blurry. I have reverted back to version 5.3.1 and it works again, but I don't have the latest functionalities (map cache for offline navigation for instance). I have also searched and realized other devices also have this issue with android 2.2.1 :
http://www.google.vu/support/forum/p/Google+Mobile/thread?tid=2c9a34f9fbb86a77&hl=en&start=40
Do any of you MiniCM6 users have this issue ?
raphaelc said:
Hi.
I have just installed MiniCM6 on my X10 Mini and I have everything working great. I have updated Google Maps to the latest version (5.11) from the market, and since I have a problem with Google Navigation : navigation does not re-route and map underneath route stays blurry. I have reverted back to version 5.3.1 and it works again, but I don't have the latest functionalities (map cache for offline navigation for instance). I have also searched and realized other devices also have this issue with android 2.2.1 :
http://www.google.vu/support/forum/p/Google+Mobile/thread?tid=2c9a34f9fbb86a77&hl=en&start=40
Do any of you MiniCM6 users have this issue ?
Click to expand...
Click to collapse
Maybe its better for you to upgrade to CM7 !???
martiii said:
Maybe its better for you to upgrade to CM7 !???
Click to expand...
Click to collapse
I wish so, but I saw too many people posting problems on this forum after updating to CM7, and revert back to CM6.
raphaelc said:
I wish so, but I saw too many people posting problems on this forum after updating to CM7, and revert back to CM6.
Click to expand...
Click to collapse
OK i think that´s history , im on miniCM7 by nAa look here and its by far the best rom i´ve installed on my mini ever its pretty fast and stable.Try it on ur own i promise u will dont regret it.
Look at this Thread read carefully installation guide when questions the FAQ by matmutant and be happy ... nothing to say.
martiii said:
OK i think that´s history , im on miniCM7 by nAa look here and its by far the best rom i´ve installed on my mini ever its pretty fast and stable.Try it on ur own i promise u will dont regret it.
Look at this Thread read carefully installation guide when questions the FAQ by matmutant and be happy ... nothing to say.
Click to expand...
Click to collapse
Are you sure it's stable ? Does the camera work fine ? Are there any issues remaining concerning wifi, data, or gps ? Are there any recent reports on system crash or reboots ? Maybe I will install it this evening...
Please post queries and requests for help in general or Q&A.
Sent from my E10i using XDA App
raphaelc said:
Are you sure it's stable ? Does the camera work fine ? Are there any issues remaining concerning wifi, data, or gps ? Are there any recent reports on system crash or reboots ? Maybe I will install it this evening...
Click to expand...
Click to collapse
Yep, cam works at 5mp only the video recording is a little bit sluggish but i think nAa fix this problem in the next few updates.wifi , data and gps works fine.since i´ve installed this rom i never had any random reboot or system crash.
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Thats new bug you phased not anyone tell about and not im phasing any that thing
v2.2 and v2.3 are almost same just few things like odexed and some fix not much other thing
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
I got this too http://forum.xda-developers.com/showthread.php?t=1271268
I don't have that bug... did you flash the framework for v2.2 before flashing 2.3? maybe this dosn't afect to the touchscreen but just only to see what was your flashing process.
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
acesteady said:
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
Click to expand...
Click to collapse
moded framework allready gave in rom
touchscreen prob of keypad you tell is not happen atall in my phone
Im reply all things from my phone not from pc means not phasing that stuff yet
will try to solve for those phasing in new version
adeklipse said:
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
Click to expand...
Click to collapse
thanks for the quick reply nims, just info for you the bug that I found is just exactly the same as adeklipse said
acesteady said:
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Click to expand...
Click to collapse
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
icemanhi said:
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
Click to expand...
Click to collapse
And "#throwinag##"% fthus akernael wdill make it wsorks,h rigsht?
This is the text that I typed without any correctionss
And "throwing" thus kernel will make it work, right?
Sent from my GT-S5830
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
adeklipse said:
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
Click to expand...
Click to collapse
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
acesteady said:
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
Click to expand...
Click to collapse
Yep, I went with flashing the non-oc kernel as well. Underclocking will still leave you with the problem.
Sami-sami.
*ane orang Banjar nyasar ke Bandung, gan.
Sent from my GT-S5830
I use 800 MHz on oc kernel and not facing this problem.. maybe I'll try above 800..
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
adinq said:
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
Click to expand...
Click to collapse
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
I also have the same Problem.
It was all fine with froyo 2.2, when i switched to stock 2.3.3 kpe or 2.3.4 kph this problem occured. It stopped happening with 2.3.3 kpy and its perfectly fine with the 2.3.5 stock firmwares.
My big problem is, i cant use any custom roms, it happens with every single custom rom.
So it's not really a warranty issue when it happens with custom roms. Coz samsung could say it works fine with stcok firmware, 2.3.3 kpy for example.
I really don't know what the cause of the problem is, because my friends galaxy ace doesnt have these problems with the custom roms i tried.
I'm not sure but besides the kernel i kinda think it might be a battery issue, because it happens less frequently when its plugged to the charger.
adeklipse said:
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
Click to expand...
Click to collapse
may be this mod can help you..
http://forum.xda-developers.com/showthread.php?t=1365434
i OCed to 883MHz without problem on touchscreen
matur nuwun
aku wong solo bro...╋╋ム ╋╋ム ╋╋ム =)) ╋╋ム ╋╋ム ╋╋ム
pls press thanks button if you like this.
sorry for my bad english