Related
I have swype and I am finding that after installing it on my rooted odexed 2.2 rom it is buggy. Words aren't typing well and there seems to be a fair amount of ghost touch typing.
Is anyone experiencing problems? Have you fixed them?
EDIT: After uninstalling and reinstalling the program again, it seems to have fixed a lot of the issues. i am using version 1.56.30.7625.
They need to post a new version of this
I have swype not respond to word-swypes all the time.. changing input type to something else/switching back fixes it.. (this didn't happen in 2.1..)
-mark
Works perfectly on CM6 (AOSP FroYo). Worked perfectly on DC 3.2.3 as well. Never had any issues with the latest Swype.
I guess I should have included that I'm using the Stock Official 2.2 Odexed ROM...It worked perfectly using Whitslack's 1.47 before I flashed the upgrade this morning. Guess waiting patiently for the next version is the best course of action...
Or perhaps if CM gets 4G working...I could switch to that :-D
As some of you have come from the captivate know what I did there with Rom Q&A threads. I am doing the same here. In an effort to clean up the site. All Rom related question shall from now on be posted in the proper Q&A or will be deleted on sight.
So was it strange that I was never told this thread even existed and had no idea until just now? For anyone still having problems, a few troubleshooting techniques:
-When installing, are you sure you cleared cache and dalvik? If coming from a major release to a major release, did you do a full wipe instead?
-Are you using the proper radio, as posted in the first post of the thread?
-Are you using any task managers or antivirus apps?
i just flashed 1.2.11 to my phone which i decided to finally root after about 4 months, and i love it. I installed barnacle due to the stock hotspot debacle and when i go to use it it tells me that NAT is not connected. now here at work, where i am testing it, i dont have great connection but i can get 3g to work here. what does it mean when NAT does not connect?
Sorry, no answer here on the hotspot issue. Have you PMd Mister ClearD? He is very responsive and has been working hard on this whole hotspot issue... he'd likely be very interested in your problem.
I too am running 1.2.11, and am delighted with it. However, I am wondering if there is any way to get more volume out of the speaker for ringtones and alarms. I have them maxed out on the phone's adjustments, but it's still awfully quiet.
Michael look for an app called volume+ made by meltus I believe in the market. It works with gingerbread but not froyo. There is a few other fixes for the volume limit but I can't link them currently because I am on my phone. Do a search for it and it should come up. If someone doesn't post it up.
Sent from my Desire HD using XDA App
Thanks, got it and it does help!
i sent him a PM. if he gives an answer that works i will post it and let everyone know.
Hello,
Last night I flashed the latest ClearDroid ROM 1.1.51, but when I check under the software information menu, it says the Android version is 2.2.1
The flash seems to work because it says it's running Cleardroid.
Shouldn't it be running the Gingerbread (2.3) update or am I mistaken?
Also, the data connection seems to screw up, and only works when it wants. Sometimes ROM Manager will disappear from the apps menu.
I did a full wipe before flashing and it still won't work.
I also just flashed CoreDroid and it did update to 2.3 , but I want my stock HTC theme back!
Thanks!
marcano said:
Hello,
Last night I flashed the latest ClearDroid ROM 1.1.51, but when I check under the software information menu, it says the Android version is 2.2.1
The flash seems to work because it says it's running Cleardroid.
Shouldn't it be running the Gingerbread (2.3) update or am I mistaken?
Also, the data connection seems to screw up, and only works when it wants. Sometimes ROM Manager will disappear from the apps menu.
I did a full wipe before flashing and it still won't work.
I also just flashed CoreDroid and it did update to 2.3 , but I want my stock HTC theme back!
Thanks!
Click to expand...
Click to collapse
The version 1.1.51 is still on froyo build but has the new ril for gingerbread. On the first page of the Dev post he has a link to the matching radio. Give it a flash and see if it helps with your data connection. If you want gingerbread his version 1.2.xx is the gingerbread Rom (still in beta), it has the fix for messaging but he is still working on tethering. It's still the stock look to the dot
On the app side I don't know what could be going on there, sorry I couldn't help on that point, (since I'm not having that particular error)
Sent from my Desire HD using XDA App
marcano said:
Hello,
Last night I flashed the latest ClearDroid ROM 1.1.51, but when I check under the software information menu, it says the Android version is 2.2.1
The flash seems to work because it says it's running Cleardroid.
Shouldn't it be running the Gingerbread (2.3) update or am I mistaken?
Also, the data connection seems to screw up, and only works when it wants. Sometimes ROM Manager will disappear from the apps menu.
I did a full wipe before flashing and it still won't work.
I also just flashed CoreDroid and it did update to 2.3 , but I want my stock HTC theme back!
Thanks!
Click to expand...
Click to collapse
im personally running 1.2.12 RC2 which is his latest Beta, along with the suggested radio. i dont have any problems with network and it looks and behaves great while keeping that stock look. honestly i love this ROM. if you have any major questions just send ClearD a PM and he will get back to you. probably my favorite dev because he is so thorough and responsive to his followers.
Pytheous said:
i sent him a PM. if he gives an answer that works i will post it and let everyone know.
Click to expand...
Click to collapse
to post my own answer ClearD told me that 1.2.12 has a working tether program. he is still working on making the stock tether work but for now the one he has included in the rom works great so no need for barnacle
Thanks Pytheous and Hiyabuz! I'll give the latest beta a shot because last night I flashed the rooted AT&T stock rom and my battery life improved but I'm still having data problems. Now I'm not sure if it's my cell company or the ROM that's causing the problems.
I'm afraid of flashing the radio and losing my signal completely!
marcano said:
Thanks Pytheous and Hiyabuz! I'll give the latest beta a shot because last night I flashed the rooted AT&T stock rom and my battery life improved but I'm still having data problems. Now I'm not sure if it's my cell company or the ROM that's causing the problems.
I'm afraid of flashing the radio and losing my signal completely!
Click to expand...
Click to collapse
This ROM, from what i can tell, is basically a stock ROM with all of the bloatware crap taken out, and a few cool gadgets added here and there. I love the ROM and the way it feels, but what i love the most is the responsiveness of the Dev for the ROM. If i have an issue i just send him a PM and he either sends me an answer or gets to work on it right away.
as for the radio i flashed the reccomended one on his original dev post and i actually get better signal in most places.
I also have another question of my own. i wanted to test out the GPS last night and it seemed a little more sluggish than stock. i could be immagining things but i was wondering if anyone else was having this problem also.
Pytheous said:
I also have another question of my own. i wanted to test out the GPS last night and it seemed a little more sluggish than stock. i could be immagining things but i was wondering if anyone else was having this problem also.
Click to expand...
Click to collapse
He has already inserted the fix in the Ron you have to let it lock a few times then its faster than stock
Sent from my Desire HD using XDA App
Hiyabuz said:
He has already inserted the fix in the Ron you have to let it lock a few times then its faster than stock
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
ok thanks buz. i just wanted to check
i only used it for about 3 min so it wasnt a very good judge of use
For example yesterday I retried mine first reconnect of gps after upping to new radio took 5 mins without vase and was sluggish. With case it took almost 10, today with case on first lock took 14secs with an 8 sat lock inside and using my case. its been awesome since he put in the gps fix. B4 it could take up to 30 mins for first lock without my case and it was only like 4 sats.
Sent from my Desire HD using XDA App
Noob here, I flashed the ClearDroid 1.2.12 rom a couple of days ago and love it. The only thing i want to change is the secure box in the messages menu. I would like to hide it or remove it, is it possible? Any help is appreciated, I did search I swear I did.
Will the Tiny audio fix work with this rom?
Issues with using latest gingerbread build.
Hello CleardDroid team;
I am a big fan your ROM, it works great on my phone. I have some serious issues using this ROM;
1) I am unable to compose message, when i try to compose message it force closes. I have tried alot to fix the issue but unable to resolve it. I have cleared its data, restarted it, fix the permissions using ROM manager, but failed to fix the issue.
2) Hotspot is not working, but I guess you are working on it.
Just updated to the latest CM7 Nightly, and so far twice today, when I went to hit the sleep button. The screen remains black. I can see a blacklight go on though or something, as the screen changes from when its in sleep. But it remains black.. Is this a known bug? Any suggestions? I would really hate to have to go back to Weapon as I spent all day setting up CM7.
edit: upon further investigation, this appears to be called sleep of death? Are there any known fixes for it?
I had the same problem, happened with every cm7 based rom....i tried posting my problem on this forum for help but no 1 really had any idea what was the issue or how to fix it...as far as I know we're stuck using 2.3.3 roms
Btw do you have a wind optimus 2x or a tmobile g2x? Mine is from wind
Sent from my LG-P999 using XDA App
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
jamadio said:
Faux123's 0.4.4 kernel has a patch for it. It will work with CM7 nightlies.
Click to expand...
Click to collapse
Will it only work with the nightlies? I would've preferred to use the stable release or the cm7 eagleblood
Sent from my LG-P999 using XDA App
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Thanks for posting that, I was about to test it myself
Sent from my LG-P999 using XDA App
I think there are 2 different sleeps of death, one of them only happens sometimes, whereas the one we get happens every single time the screen turns off
Sent from my LG-P999 using XDA App
hopefully we can fix this problem together.. It seems Cm7 has better battery life then the other roms so I would hate to go back.
well weapon has been pretty good for me...can't complain really...which CM rom did u try with faux's kernel?
The very latest nightly. Cant remember off hand which one it is.
Also, If I flashed weapon right now (being on CM7 + faux kernel), will I retain the faux kernel? Or will I need to reflash faux's kernel. And even though this kernel says CM7, will it still work with weapon?
I believe the kernel would be flashed over by the stock kernel in weapon, if it doesn't get flashed over then i doubt your phone would be able to boot up, because the kernel shouldn't be compatible with stock 2.3.3
give a shot and try it out, also if you want to over clock on weapon there should be another kernel by faux that u can use, look for it in the development forum
I am going to stay a little longer on CM7, maybe someone can help me with these SOD's.. Then I guess I wil go back to weapon or try out that eagle one. Not sure which is better..
i think the stock eagleblood is very plain and clean....i like weapon because its a little more customized, plus its the only stock rom that has the notification power menu...and from the looks of it, our problem seems very rare so i don't think anyone has or will develop a fix for it
---------- Post added at 02:07 AM ---------- Previous post was at 01:16 AM ----------
hesher said:
i installed his latest CM version along with the CM rom and it happened still. Is there a seperate patch? or is the kernal on its own supposed to fix it?
Click to expand...
Click to collapse
i ended up trying it for myself even though it didn't work for u, and it actually ended up working for me
i'll give u detailed steps for what i did and maybe it'll work for u too
(this is all on CWM recovery)
after backing up i factory reset (wiped data), wiped cache, wiped dalvik, and formatted /system
then i flashed the latest CM7 nightly (195), then i flashed gapps
i wiped cache and dalvik again then i flashed faux's 0.4.4 CM SV kernel
i then pessimistically rebooted and voila for the first time i had a functional CM7 rom....i've put the screen to sleep about 10 times so far and it awoke every time so i think it should be fixed
I hope it works for you. I probally didnt see my first SOD until maybe 50 or 60 sleeps.
well I used to get the SOD on the first sleep so its definitely an improvement for me...i'll let you know if it lasts i guess
I just flashed to CM9. Tried stable, and latest nightly. The home button does not seem to work?
It is not completely dead though. It lights up when touched, and vibrates. Just no action?
Didn't have that problem at all mate. I'm not currently on CM9 Stable, as I've gone back to VI for battery testing for now. But it was definitely not an issue for me.
I'd suggest doing a factory reset/wipe and flashing again. I assume you are using 3.33?
Sent from my CM9 Stable Sensation using XDA Premium
These kernels are for CyanogenMod 10 - Alpha 4.
The goal of these builds is to fix the issues with phone signal, which is not properly working with the stock kernel. Nothing was changes, no extra features, no nothing.
There won't be any more "development" now that the bug is fixed.
The experimental sync bug fix, as the name says, it's a new sync bug fix I was testing. It's here because it partially fixed the missing signal issue at first, but it's not the real fix.
Downloads:
kernel-cm-10-A4-signal_fix.zip: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-exp.zip: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore.zip: stock alpha 4 kernel.
Note: I forgot to change the "name" of the kernel, so you'll get [email protected]_CM9. Don't worry, it's for CM10
Even though I marked V2 as experimental build and I added it as alternative choice, it's the most downloaded version.
As I reported several time ago, mobile data is maybe less stable with it and I think it's because the PDA state is controlled with early suspend instead of the regulr suspend, as it was in the old Samsung releases. In case of problems, flash V1.
If you noticed anything, please report
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patches attached, applied as indicated above.
I verified that when a stock ROM is used, GPIO 126 is normally set to 0.
UPDATE
Click to expand...
Click to collapse
If you are stuck at Samsung splash screen and you are unable to reboot in recovery (I don't know why some users are facing this issue), so you are not able to flash another kernel or restore a backup, you can try to flash one of the kernels with ODIN.
Downloads:
kernel-cm-10-A4-signal_fix-ODIN.tar: dhiru's kernel + signal fix [0001, 0002] - (previously known as V1)
kernel-cm-10-A4-signal_fix-ODIN-exp.tar: experimental sync bug fix [0003, 0004] + signal fix [0001, 0002] - (previously known as V2)
kernel-cm-10-A4-restore-ODIN.tar: stock alpha 4 kernel.
Reboot in Download mode and flash as PDA.
Kernel modules are not included in the PDA. They are not necessary if you were using dhiru's CM with no custom kernels. If you are not sure, do as follows:
Flash kernel as PDA with ODIN (assuming you are stuck at Samsung splash screen and can't reboot in recovery)
Reboot in recovery (pull the battery if nothing works and use the three-keys combo)
Flash CyanogenMod 10 zip (your data will be preserved)
Flash once again kernel as PDA with ODIN
_____
Older posts:
Update: Now I know what stock ROMs use (GPIO 126 = 0). I'll soon update the kernel.
I already wrote that this won't be a custom kernel, no extra features, overclock etc. I opened this thread simply to test a fix, that's why I opened it in the general section, even though the dev section would have been more appropriate.
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
Very old post:
Click to expand...
Click to collapse
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Question
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
jsp1984 said:
Hi loSconosciuto, i have one question regard alpha 4. I have problem with signal too (as i posted in alpha 4 general thread) but i think it is beacuse my modem (LUBKPD) has been overwrite to DDLE1. Is there any posibility to create a flashable zip only to overwrite my (our, for those who live in south america and has the same problem). Sorry to ask you but i do not know what to do, cause my media storage don't get recognize and i can`t back to stock rom and no one reply my question in general, my phone is practically a stone, except for that moment when get signal (sms and calls only). Thank you!
Click to expand...
Click to collapse
I could, but I don't have LUBKPD modem.
All you have to do is to take modem.bin from the PDA of your ROM (as you may know, you can open it as a normal tar), copy it in /radio overwriting the existing one and reboot. Permissions will be automatically set on reboot.
If you want, here two (different) flashable zips I made for myself. You have to replace modem.bin inside of the zip with yours and then flash.
radio-cm-XXLE4-galaxysl-signed.zip (will erase /radio and then copy the modem)
radio-cm-KPU-galaxysl-noerase-signed.zip (will simply copy the modem)
Works perfectly. Thank you dear Sir :thumbup:
Sent from my GT-N8013 using xda app-developers app
Ok, I think I almost fixed the problem. sec_get_param_value is an exported symbol defined in param.ko (yeah, brilliant...), but we don't use that module anymore in alpha4. The consequence is that the function that turns on the modem is never executed completely.
It still needs some improvements. switch_sel is never set or initialized, but at least the connection is immediately enstablished now. The problem is that I'm not sure which is the best option, so I'll wait for more opinions about it.
In the meanwhile I built two new kernels:
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
V2 is a little bit more "experimental".
OP updated with the new patch.
__
Maybe this is not the right place for this thread, but I opened it here because there won't be any development.
I flashed the V2 and I got the signal instantly after flashing
Sent from my GT-I9003 using xda app-developers app
Thanks man it works great for me...flashed v2 and boom it turned on
Sent from my GT-I9003 using CM10 alpha4 Tapatalk 2
It works so good thank you so much I hope you will continue your very good job
Envoyé depuis mon GT-I9003 avec Tapatalk
Its working fine till now, Thanks alot!. I just wanted to say would you please add move governers in the subsequent release
This thread should be moved to development section.
So that people are aware of the fix.
And it works perfectly, thanks to losconsiuoto
Sent from my GT-I9003 using xda premium
hi
loSconosciuto said:
I'm lazy, so read this post.
kernel V1: includes only the sec_get_param_value fix
kernel V2: includes both the first change (the reworked sync bug) and the sec_get_param_value fix
As I posted in dhiru's thread, with my kernel I catch the mobile signal faster than with the stock kernel. I don't have to wait, all I have to do is to turn off and then on the screen once.
I've recently done some changes to my kernel regarding the sync bug. So, suspecting those changes are what makes the difference, I applied the same changes to dhiru's kernel and built it.
I tried to reboot few times and there's really a difference, at least for me.
I suspect that with the stock kernel there are only issues in reporting the current intensity, because 3G and calls seem to work.
Download: (Flash from recovery)
kernel-cm-10-Alpha4-TEST.zip
kernel-cm-10-Alpha4-RESTORE.zip
Source code:
android_kernel_samsung_latona at 0e84cc4896 + patch attached + unset CONFIG_SVNET_WHITELIST
I don't know if battery life is affected, if the sync bug is really gone (no issues till now) or if there are issues with this kernel (I'm not using it. I only tested it for a few minutes). Flash at your own risk.
Don't report any bug in CM10 thread if you are using this kernel. Use the restore zip first, try to reproduce the bug and then report.
Click to expand...
Click to collapse
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
rahul_rocks3 said:
first tell me which rom were u on, and did you update to cm10 alpha 4 and followed all the instructions properly as mentioned
Click to expand...
Click to collapse
I wrote some of the original instructions on the i9003 forums, so procedure/method is not a problem here.
I think the issue is I flashed the v2 kernel over the ParanoidAndroid latest 2.54 Alpha4 assuming that as the base is this ROM, the kernel would work. But got a soft brick. Its all fine now, had to go through the whole KPE, LF2 process and now flashing CM10 Aplha4.
If you could just tell me if replacing the modem.bin from LF4 is enough for the signal issues or do I still need to flash the V2 kernel?
Thanks in advance!
EDIT: Flashed V2 but got a 2nd soft brick. Went through the whole process again () My signal and data are working but the indicator is greyed out.
resolved problems
I had problems relating to signal strength and storage.
Thanks and its now working perfectly.
---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------
rahul_rocks3 said:
After i flashed with the CM10 alpha 4 the first problem i found the signla problem but thanks to your great hard work it was solved so easily and that too without any errors.
Request to Moderators Please move this thread to Developement or merge this post under the CM10 alpha 4 update
Click to expand...
Click to collapse
+1
Flashed V2... It's working great. Thanks.
Sent from my Nexus 7 using xda premium
Thanks works like a charm.
spacebar2011 said:
Well, flashed V2 and device is stuck at the initial Samsung screen. It won't even boot into recovery. Anybody face the same? My cousin is furious right now!
Click to expand...
Click to collapse
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
arindammanidas said:
Spacebar! How the heck are you?
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Click to expand...
Click to collapse
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
spacebar2011 said:
I'm very well mate, you? :highfive:
Just been off the radar due to a choked studio schedule. I've been somewhat active on the One X forums though.
Cousin asked me to update his SL (passed on from me) and this happened last night. I'm not sure whether to flash the v2 kernel again as signal etc is working but the icon is all grey and it takes about 15 mins after a reboot to get signal. Don't have the time to go through the entire clean flash process all over again.
Click to expand...
Click to collapse
I'm doin' good!
I'm still on CM9.... but v2 seems to work for some people including loSconosciuto himself....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !