hey guys, i am running JACXHERO 1.8 and i love the rom, one problem though. when i flashed the rom i had that text box with the circle around the M and it wouldnt go away so i just de-selected touch input and then pressed home, and tried to go back to settings and enable it again, but now i cant even access locale and text, when i click on it i get a FC. if i remove HTC_IME.apk via appmanager i can access the menu... i have tried pushing HTC_IME from the .zip file of the rom and no luck... i am about to try an older HTC_IME. you guys have any other ideas, or a way that i can enable Touch Input without accessing that Locale and text menu?
Long press hold on a text box and it will have a menu allowing you to select Input Method.
h.nocturna said:
Long press hold on a text box and it will have a menu allowing you to select Input Method.
Click to expand...
Click to collapse
i rememeber seeing this on other builds, so i know its possible, but when i long press i dont get any options that come up. i can copy and paste but thats about it.
palosjr said:
i rememeber seeing this on other builds, so i know its possible, but when i long press i dont get any options that come up. i can copy and paste but thats about it.
Click to expand...
Click to collapse
Probably because you disabled On Screen Keyboard via the Locale and Input Menu... not much you can do to fix that other than re-flash the ROM. =/ Sorry.
h.nocturna said:
Probably because you disabled On Screen Keyboard via the Locale and Input Menu... not much you can do to fix that other than re-flash the ROM. =/ Sorry.
Click to expand...
Click to collapse
ok thanks. quick question. can i just reflash without wiping everything? i know its a noob thing to ask but wouldnt the reflash just fix anything i have changed as far as the ROM is concerned. if not no biggie i can restore all my apps, i just was trying to find an easy way to get it working
@ palosjr: did you ever figure this one out? i'm having the exact same problem and I've flashed the ROM like 7 times, but nothing helps.
Related
I know this does not really belong to development but I figured most of the people who want to do the update will come here... Please move the thread if you deem fit, mods ^^.
Anyway, I can't confirm if the method works since I'm rooted myself, but have found the following:
Hi,
I have found out a way to update the Nexus One to the new OTA that Google is pushing through, the one including multi-touch everywhere.
Go to the URL below:
http://www.mediafire.com/?rgnjl4hqmmi
and download.
Then save on to your sd card, not in any folders, and rename it update.zip (windows users just rename it update, .zip will come by itself)
1) Turn off your phone.
2) Turn on by holding down Power and the Trackball
3)Select Bootloader (Selection instructions on the top of screen)
4)Select recovery
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
8) Enjoy!
All the credits go to Fabolous from AndroidForums.com
Click to expand...
Click to collapse
Source: http://forums.t-mobile.com/t5/Nexus...3;jsessionid=237BA996FE5094EB98964E024CF21502
Also, in case you don't trust the MediaFire link, here's the Google One: http://bit.ly/9vvioF
Hope it helps.
I can confirm this method works for non root users. The MT is awesome, to say the least.
When I select recovery it shows a picture of an android next to a triangle with an exclamation point in it. I renamed the file and put it in the sd card, what am i doing wrong?
Unicellular:
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
:\
Wysie said:
Unicellular:
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
:\
Click to expand...
Click to collapse
Did you try pressing power and vol up at this stage? #5 isn't really a step, it just happens. I figured this was a given, but I guess not.
indiearmy said:
Did you try pressing power and vol up at this stage? #5 isn't really a step, it just happens. I figured this was a given, but I guess not.
Click to expand...
Click to collapse
Ya I had assumed that after selecting recovery the android should be next to a box but i did vol up and power down. It is working so far!
I've downloaded the file twice and I'm getting a caution icon with the android-bot. Any ideas as to what could be wrong?
I've also use two different sdcards.
Thanks for any assistance.
B3astofthe3ast said:
I can confirm this method works for non root users. The MT is awesome, to say the least.
Click to expand...
Click to collapse
Second that...this is very cool.
Redeye said:
I've downloaded the file twice and I'm getting a caution icon with the android-bot. Any ideas as to what could be wrong?
I've also use two different sdcards.
Thanks for any assistance.
Click to expand...
Click to collapse
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.
hi Unicellular,
can you be more specific, i have also the same problem, and could not see any bot near a box, after selecting recovery first colored cross is seen then a bot with a triangle comes up.
Does this use the new kernel?
Trackz said:
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.
Click to expand...
Click to collapse
Thanks!! It worked.
I think I had the caution icon because of the following.
E:Can't open /cashe/recovery/command
System is back up with multi-touch goodness.
what do you mean?
"The one including multitouch everywhere??"
the multitouch for me only works in the browser maps and the gallery
is there on that includes a multitouch everywhere??
lazoman. I was at the screen with the caution and android-bot too.
It's not really a quick press of "Vol. Up + power button" I kinda just spammed both buttons until it worked.
Trackz said:
I got the same thing...while at that screen, just did the volume up and power button and it gave me the option to install it.
Click to expand...
Click to collapse
I can confirm that this worked for me too. Thanks!
This update took away the haptic feedback when I press the little dots in the main screen to go 'left' or 'right'. Anyone know how to get it back again?
Does this update also apply the new radio update?
Does this method void the warranty or violate the TOS?
What about rooted devices ?
Why can`t i use this update if my phone is rooted ?
christiankk said:
This update took away the haptic feedback when I press the little dots in the main screen to go 'left' or 'right'. Anyone know how to get it back again?
Click to expand...
Click to collapse
Those buttons don't have haptic feedback (i havent updated yet and just checked)
Hey guys
I managed to root my device with the first guide (oneclick) and uninstalled alot of LG crap, same time i uninstalled the LG launcer. - Today i got a problem with my device. I couldnt ring and hear people when i manged to get in contact.
I decided to factory reset the phone, but my problem is that i dont have any launcher now. When i do the hard reset thing (vol down + home and power on) i can get to the screen where i can type in pin code, but after that there is black screen cause there is no launcher. The search function dont work but the notification bar is working. so i cant get to the market and install. Mostly it just shows the LG logo when the phone is turned on and the touch screen is working cause it makes the click sound. But nothing else.
Does some one have an idea to how i can get a launcher installed ??
thanks in advance
Please use search function. This problem is already discussed here. You have to use ADB.
Sent from my LG-P990 using XDA Premium App
Sorry the other threads i found was about how to get other launchers. But i will try read deeper into to threads then ;(
nafaikon said:
Hey guys
I managed to root my device with the first guide (oneclick) and uninstalled alot of LG crap, same time i uninstalled the LG launcer. - Today i got a problem with my device. I couldnt ring and hear people when i manged to get in contact.
I decided to factory reset the phone, but my problem is that i dont have any launcher now. When i do the hard reset thing (vol down + home and power on) i can get to the screen where i can type in pin code, but after that there is black screen cause there is no launcher. The search function dont work but the notification bar is working. so i cant get to the market and install. Mostly it just shows the LG logo when the phone is turned on and the touch screen is working cause it makes the click sound. But nothing else.
Does some one have an idea to how i can get a launcher installed ??
thanks in advance
Click to expand...
Click to collapse
Hello my fren.. Did u in the 1st place had made backup or ur rom via nandroid before removing stuff from ur rom? If yes then its too bad.. But there is always an alternative..
1. Download a custom available here and place it in ur mmc card.
2. I presume that u have paulobrien 3.0.1.4 r1 - ClockworkMod Recovery for the LG Optimus 2X installed then flash it via clockwork.
3. Enjoy ur new fast phone!!
naah i did not backup.. thought i would never need it.. but i was wrong..
so here is what i did.
When the nortification bar was working i went into the musicplayer from there, in there i managed to get the search funtion in albums wich gave me the opportunity to search on the internet via the browser (wich i could not open or find cause no launcher ).
I went to 4shared from there and found a launcher but i could not install it because the installing from other source funtions was disabled. Fortunately it gave me the option so i could enable it and i did.. AND YEEEHA i manged to install a launcher and retsarted and it dos work !!!
Before when i pressed the home button it just restarted the phone i could do nothing ! only black screen with logo.. so i reset it and tried the above...
it seems that my phone is still rooted, cause i have the "superuser" thing but when i get time i will unroot it and sell this crap of a device and get back my old Nokia N8 again
Don't just root your phone without learning how to actually use the powers it gives you. If you remove anything from /system you will not be able to restore it with factory reset, because factory reset relies on what is in /system. But I guess you figured that out the hard way.
Learn to use ADB and nvflash, nvflash being the easiest based on the guides at 2x.modaco.com. ADB can get you out of most trouble by editing/replacing single files and nvflash will enable you to overwrite all partitions, i.e. with a stock ROM.
Everything you need is in these forums or in the wiki.
yea the hardway was more fun ;-) (actually not )
I was trying the ADB way, but my computer didn regonize the phone so it was difficult
Now i just need the stock apps and launcher so i can unroot it again
start off with this page:
http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
once you have restored the stock rom you can now delete the clockwork recovery by using this:
http://forum.xda-developers.com/showthread.php?t=1021554
after that unroot in superoneclick and your all done.
nafaikon said:
naah i did not backup.. thought i would never need it.. but i was wrong..
so here is what i did.
When the nortification bar was working i went into the musicplayer from there, in there i managed to get the search funtion in albums wich gave me the opportunity to search on the internet via the browser (wich i could not open or find cause no launcher ).
I went to 4shared from there and found a launcher but i could not install it because the installing from other source funtions was disabled. Fortunately it gave me the option so i could enable it and i did.. AND YEEEHA i manged to install a launcher and retsarted and it dos work !!!
Before when i pressed the home button it just restarted the phone i could do nothing ! only black screen with logo.. so i reset it and tried the above...
it seems that my phone is still rooted, cause i have the "superuser" thing but when i get time i will unroot it and sell this crap of a device and get back my old Nokia N8 again
Click to expand...
Click to collapse
What do you want for the phone - lol?
Funny how when ever some user messes up something - then its the device that is crap
Ehmm the deivce is crap... the sounds is terrible.. and the reason why i messed up was i had problems with the device. When i call some one they cant hear me and i cant hear them.. same with income.. but i can text msg.. and its not my carrier or other stuff.. it is the ceappy device ;-)
Since yesterday I have the following problem:
If I take my OB from the power plug and close the screen with the "lock" - button (top right) to turn off, the Screen remains black.
I can press any key but nothing happens!
Only when I take the battery out and re-launch it works again OB. At least until I turn off the screen again. However, the mobile is connected to the AC adapter or via USB connected to the PC, I have no problems until now!
I hope anyone cold help me!
THX Marduk
At least you also mention your system configuration, Stock ROM, CM build, kernel, etc.
I´m using the CM71 Nightly withe the Nova2.6.35.7 v11c Kernel. The build No. is GWK74.
Can you take logs? First you have to activate log module via Nova Application, then reboot.
I made the log file.
Where can i find it to post it here? By the way: sometimes my phone shows me the cwm bootscreen but i´ve done nothing to reboot!!! Its like i discribe in the first post.
Yes, here? upload it to pastebin, dropbox, box.net or else. If you can't post link because having less post, remove your http:// at front of your link, or code it with
Code:
I mean where can i find the logfile? Where is it stored on my phone?
Marduk666Nor said:
I made the log file.
Where can i find it to post it here? By the way: sometimes my phone shows me the cwm bootscreen but i´ve done nothing to reboot!!! Its like i discribe in the first post.
Click to expand...
Click to collapse
post it on pastebin.com and post the link here
have you set the "G" button on Nova Configuration?
no i haven´t done it. I didn´t know i need it to do!
Marduk666Nor said:
I mean where can i find the logfile? Where is it stored on my phone?
Click to expand...
Click to collapse
Ouw, sorry, you can catch log with app, like this one https://market.android.com/details?id=com.nolanlawson.logcat
Make record with it, then reproduce your problem..
Marduk666Nor said:
no i haven´t done it. I didn´t know i need it to do!
Click to expand...
Click to collapse
try to set it first
maybe that triggers the problem
I can´t reproduce it by myself. it happens when my phone want it to do!
Marduk666Nor said:
I can´t reproduce it by myself. it happens when my phone want it to do!
Click to expand...
Click to collapse
okay lemme get this straight
aprold said (i believe i red it somewhere), when the first time you flash his v11 kernel, the G button wasn't assign to anywhere
and when you reboot, the system replace the keylayout with his keylayout
with the null G button variable, i believe this make an error and create an empty keylayout to the hard button
at least that's what i tought
Ok! i´ll try it! Where can i change the setting of the "G" button? is it in the Nova menu?
yes,it's on the Nova Setting
but i'm not saying it'll work 100%
just trying to help
It looks like it is working! Let´s see what happen the next few minutes/hours/days!
Thank u all!!!
It was the G button! Thank u guys for the great help!!!
Sent from my LG-P970 using XDA App
u're welcome
I searched in the Rocket, midnote and Criskelo threads but I couldnt really find any solutions. A few people have had same issue but I couldnt find any solutions.
I have tried all of the above ICS roms and they all work great other than the fact that the home button does not work to go home. It will wake up the device however. Am I missing something?
Also searching.
Until yet only got to know its the ICS Pre-Keyboard causing a remapping of the Numbers assigned to functions (Hardkeys)
My homebutton isnt working either anywhere but it can unlock the device (Escape Lockscreen)
Yet trying to find out whats the keynumber in the generic.kl (/system/usr/keylayout) to assign the "ESCAPE" by myself to the correct number. Hope it helps - also heard rumours talking about its a driver issue - i dont hope so ...
Maybe someone with a note (edit: [email protected]) could post his "generic.kl", maybe theres a simple difference and we could easy get rid of it ;-)
I had the same issue even after a full factory reset and reroot. It happened with the chinese leak and with midnote. I'd give anything for a solution to this problem.
The funny thing is:
If i flash the stock buggy ICS "I9220LP1-N7000-ICS-REPACK.tar" via Odin the Homebutton is fully working (But everything else not very well ). I am doing it right now for getting a backup of the whole /usr folder.
After that i will flash the rocketrom again where the homebutton isnt working and going to try to find the difference in these keyboard files. Maybe thats all ...
Hope ill get it soon - maybe even my approach is totally wrong, but hey: try is in the eating. If it is really driver related i cant do anything to get that button working - just wait till some devs get intouch with that issue.
I'm rooting for you, friend.
Call it coincidence, but right after reading your thread, my home button has topped working too
Anyhow, in sec_key.kl, the HOME key is listed with 102. Same in gpio-keys. kl, and qwerty.kl. This value is the same across AOSP v4, v5 and MIUI rev 4a, and ROMOW V1.
In generic.kl, 102 is MOVE_HOME.
This leads me to believe that the key is indeed mapped correctly, and that changing it to ESCAPE won't work. Why? I tried something. In 'melfas-touchkey.kl' and 'sec_touchkey.kl', keycodes for both the capacitive buttons are assigned.
key 158 BACK WAKE
key 139 MENU WAKE
I changed 139 to HOME in both the files, and rebooted. The button itself stopped working, but was able to wake the phone(behaving exactly like the home key). This suggests that the problem has nothing to do with the key mapping, but the HOME action itself.
I haven't tried to change 102 with something else, but I'm about to do just that, to see if the button works if mapped to some other command. If nothing works, I'll flash the whole thing again (GB->CF repack>AOSP) and pray it works
If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution
Lance Uppercut said:
If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution
Click to expand...
Click to collapse
Yes, flashing the whole thing again works. You NEED to flash Chainfire's ICS repack before flashing any ICS ROM. Get it here : http://www.mirorii.com/fichier/3/501208/I9220LP1-N7000-ICS-REPACK-tar.html
I'm on AOSPv4.
CF's repack can be flashed via mobile/PC Odin(PC Odin will increase your binary count and give you a yellow triangle, mobile odin will NOT.)
What I did was to go to KL3 rootable GB ROM(India), root it with zergrush, install CF root kernel, then Mobile ODIN-ed to CF ICS repack. (Make sure you keep 'enable everroot' UNCHECKED. CF repack is already rooted.)
After that, you have CWM to go to any other ROM. I believe you need to flash a base and the final release for RocketRom, or MIUI.
You are my hero bloodyhippo! Set up a donate link. You've earned it
Lance Uppercut said:
You are my hero bloodyhippo! Set up a donate link. You've earned it
Click to expand...
Click to collapse
Haha
Glad to help Lance! Though this is nothing new, flashing the whole thing in the manner it is supposed to be done removes most all problems that aren't official bugs. So, it's definitely not donation-worthy, but I've added a donation email, just in case ;-)
It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.
Aw, thanks!
Lance Uppercut said:
It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.
Click to expand...
Click to collapse
I really didn't think it was that big a headache for you! You know, I didn't read most of the developer's thread, so I had no idea this problem even existed. And my button stopped working after I updated to AOSP v5, while reading this thread
Anyhow, I'm glad(and lucky ) to have helped you out! Thanks for the $$
[EDIT] I think I'll re-donate it to some dev. Now that's a lot of options
home button working again
I upgraded from Stock Samsung N7000DDLB2 2.3.6 2012 February to (18.05.2012) AlBa XXLPY Full Repack v2.2 with a full wipe.
Everything was working fine in the beginning (i had setup a pattern lock too), till I restored all apps and data. I had restored contacts, sms too after which I noticed the home button stopped taking me back other than waking up the device and there was no pattern lock either. Somehow, that had gotten disabled and reset to back to swype unlock. Now, I setup the pattern lock again and the home button started working again. Went back to swype instead of pattern(without reboot) and home button still works. Any thought on how that happening?
Hello guys...
I've trying to reach the recovery menu, but I got myself uncessful.
My X key from the keyboard are strange, for example when I go type a menssage with the physical keyboard, I press "X" and it type "dEXAW".
Also the "del" key isn't working, neither "enter" or "j" and some more...
I found this Milestone and it was locked with a password at CM7, so I downgraded it to 2.1 stock and done nothing else, I put OpenRecovery on it but I can't acess the OR cause the "x" is crazy...
All the keyboard is weird.
Please, I beg for some help.
Thanks so much
Someone knows if I need to replace this file sholes-keypad.kcm.bin at /system/usr/keychars/sholes-keypad.kcm.bin?
Another uptade...
I tried replace the files: /system/etc/motorola/12m/key_code_map.txt and OpenRecovery/bin/change_keyboard_layout.sh
But nothing changed.
The issue started when I did again the OpenVulnerable on SBF..
Im totally lost, I can't do nothing!!!! Without the acess at OR menu I can't try CM7.