Related
i know some themes change it, but i like the theme i have already. i just want to change the keyboard to a more pleasant look. is there somewhere i can find different ones to download or flash onto my rom? i don't want to use betterkeyboard app, etc.
Here You Go Buddy.
Well i skinned the stock keyboard pretty easily with a few easy techniques.
First check out my theme Ivory http://forum.xda-developers.com/showthread.php?t=612315 To see if that's what you want. I hope your familiar with themeing or this might be confsing.
-I took the latinIME.apk from cyanogens last rom
-Opened it as a zip and navigated to the res drawable folders
-downloaded the better keyboard skins i wanted (simple black and green)
-pulled the different drawable files from the betterkeyboard apps and replaced the stock cyanogen ones
-resigned apk and flashed inside my theme
sassyness77 said:
Well i skinned the stock keyboard pretty easily with a few easy techniques.
First check out my theme Ivory http://forum.xda-developers.com/showthread.php?t=612315 To see if that's what you want. I hope your familiar with themeing or this might be confsing.
-I took the latinIME.apk from cyanogens last rom
-Opened it as a zip and navigated to the res drawable folders
-downloaded the better keyboard skins i wanted (simple black and green)
-pulled the different drawable files from the betterkeyboard apps and replaced the stock cyanogen ones
-resigned apk and flashed inside my theme
Click to expand...
Click to collapse
haha thats EXACTLY what i tried to do yesterday night! except i got the acore force close thing, & im sure it's because i didn't sign it first. i had an easy auto-sign program but i deleted it a few days ago :| & now i can't find it on here anymore!
jonesyruless said:
haha thats EXACTLY what i tried to do yesterday night! except i got the acore force close thing, & im sure it's because i didn't sign it first. i had an easy auto-sign program but i deleted it a few days ago :| & now i can't find it on here anymore!
Click to expand...
Click to collapse
haha what are the odds well at least your on the right track!
I would go for editing HTC_IME.apk, just a personal preference i guess, but i think its better, and have played around with editing it a bit myself, and its pretty easy, but you need to be able to do *.9.png files.
sassyness77 said:
haha what are the odds well at least your on the right track!
Click to expand...
Click to collapse
okay i found it. but im still geting te acore force close): what could i be doing wrong?
hmmmm.
jonesyruless said:
okay i found it. but im still geting te acore force close): what could i be doing wrong?
Click to expand...
Click to collapse
Im not sure, are you using stricstons signing tool? how are you flashing it?
What ROM are you trying it on? The new CM ROMs the keyboard is now in the LatinIME.apk instead of the framework-res.apk, but if you are using one of the other ROMs, that may not be the case.
sassyness77 said:
Im not sure, are you using stricstons signing tool? how are you flashing it?
Click to expand...
Click to collapse
i dont think so, im using a modded apk signing tool i found on here, i lost the link.
and im doing
cp /sdcard/LatinIME.apk(the one i made) /system/app
in terminal emulator.
then after that the keyboard just dissappears. if i restart after that, the keyboard never shows up. if i just try to go back, i get acore force close repeatedly.
jairomeo said:
What ROM are you trying it on? The new CM ROMs the keyboard is now in the LatinIME.apk instead of the framework-res.apk, but if you are using one of the other ROMs, that may not be the case.
Click to expand...
Click to collapse
yea i know, im on cyanogen's latest.
You may want to try getting Stericson's signing tool. If it is disappearing signing could be the main issue. Since you edit it on your PC, why don't you just push it through adb after signing instead of copying it to your sd and then having to use the terminal?
jairomeo said:
You may want to try getting Stericson's signing tool. If it is disappearing signing could be the main issue. Since you edit it on your PC, why don't you just push it through adb after signing instead of copying it to your sd and then having to use the terminal?
Click to expand...
Click to collapse
the thing is though that i used the same signing tool to edit a graphic on a different app & it worked just fine.
i don't have/really know what adb OR sdk is & terminal is the easiest way i know how to do it. i mean does it really make a difference?
its been confirmed that it's not my signing tool because i used the same tool to edit a different app, a battery widget i downloaded from the market. & it worked fine. anyone else can help me?
lets get this working buddy,
Alrighty maybe try flashing the keyboard in an update.zip, just put the latinIME.apk into a folder named app. Then copy a meta inf folder from another theme download, you can use mine. Then send that to a compressed folder, resign and try to flash it. I would try that, I have never had good luck pushing with adb and pulling stuff, I stick with the easy way
yesssss i finally got it to work! it turns out i didnt need the signing tool at all. i took the latinime.apk file from a theme with a skinned keyboard, then i ONLY replaced the keyboard png's, and kept the meta-inf how it was. thanks guys for trying to help
Hi all
My rooted 7inch HD updated OTA yesterday and became unrooted.
I got it back to root no problem, and reinstalled Play. The first thing I did was disable OTA.
I then noticed that Synker, an app I use to synch the stock address book with my Google contacts didn't work so I went through the disabled OTA one by one and even after enabling them all, I still couldn't synch. My phone syncs ok with G Contacts so it must be the HD.
I uninstalled Synker and reinstalled it, but found that I can't create the widget to run it. I previously followed the steps in
http://forum.xda-developers.com/showthread.php?t=780828
to enable widgets on ADW launcher and so tried again.
Despite following the steps, I cannot create widgets, previously, it was a breeze. The instructions say to copy appwidgetpicker to system/app and though I do that, and get a confirmation message, I find it in /system instead. Is that correct? For my own development, can someone explain why confirmation is given that the file has copied but it copies into a different folder?
Does anyone know of any reason why the update should prevent widgets being created as per the above post and is there another way?
I'm considering restoring to 7.2.3 but because of the time involved thought I'd give it another go to recover the situation.
(I tried to make this post at the end of the above thread or a similar one but being noob am not allowed to post in development threads. Mods can move this to a more appropriate forum if they wish.)
No one else noticed problems moving files into the system/app folder?
It apparently now puts the files in one folder back than you attempt to according to an earlier post, try making a folder in system/app called test and placing it there, if the post was right it will place it in the app folder instead of temp, the post also read that it changed the file name'so check that as well..
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
It apparently now puts the files in one folder back than you attempt to according to an earlier post, try making a folder in system/app called test and placing it there, if the post was right it will place it in the app folder instead of temp, the post also read that it changed the file name'so check that as well..
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
strangely enough, that's correct. It also puts the folder name at the front of the file name, so filename.apk in the app folder becomes appfoldername.apk. That bit was especially confusing becase the file appwidgetpicker.apk became appappwidgetpicker.apk. I thought the 'app' at the front was because it was an app, but it was because it was in the app folder!
Creating a sub folder in system/apps sorted it out because the file went in that folder rather than the sub folder. After that it was a simple case of renaming back to the original name and changing permissions and all sorted.
Wonder why thats happening. If its an attempt at frustrating rooted devices its a bit soft.
Thanks for the pointer. Kudos to you
First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...
Anyone have a working framework-res.apk from the 7.4.8 stock ROM that has wallpapers enabled? (I did try myself in the past but it resulted in a bootloop)
If so would you be able to upload it :good:
Thanks
Odd, the latest version has a lot of safeties to prevent a bootloop. When was the version of my wallpaper fix that you used? Also you will need to know how to use adb if you plan on copying a already modified framework-res because if you copy and paste over it it could go wrong because of permissions sometimes not carrying over or the fact you would be replacing a system file that's in use.
Sent from my LG-P769 using Tapatalk
It was quite a while ago now, guess I could try again but just wanted to see if anyone had one that they had confirmed working to save any issues.
Hello gentlemen,
I'm back, with a what I hope is a minor issue. I hope someone can help me.
I have the following head unit (Universal Model):
KLD Universal model S07 - RK3181 (quadcore)
800x480 resolution - KK 4.4.4_23072015
MCU version MTCB-KLD2-V2.67 (Jul 09 2015 19:15:51)
Kernal version 3.0.36+ [email protected] #396 (Wed Jul 22 17:40:16 CST 2015)
Build number RK3188-ENG4.4.4 23072015.09:09:11
CPU ARMv7 1.6Ghz (x4)
It is rooted via the factory settings method. But other than that it is pretty much still stock (I added a cooling fan). The only other apps I add where PowerAmp, PowerAmp Toast, Xposed Framework, XposedMTC, and Lucky Patcher (I believe this app fully unlocks the PowerAmp app). I have had no issue with it for the last 7 months.
However, the other day it took a long time to bootup. Now I have some google service errors: "the process com.google.process.gapps has stopped"
I have to keep on clicking "OK" in order for the error pop-ups to close. I have to repeat this several times until all the pop-ups finally stop. Other than that, everything else is working properly. Although I notices that Xposed and PowerAmp Toast do not start (no icons on the top notice bar).
I tried going to Settings/App Manager/Google Service Framework - and then I click Forces Stopped it, Disable, Clear Data, Clear Cache, Enable. Then I reboot, but I still get the same google service errors.
Can someone please help me fix this? Any help will be greatly appreciated.
Thanks,
Galo
PS - One other thing. This is related to the XDA website in general. How can I get rid of that stupid side panel (Analysis & Opinion / More XDA New). It keeps on automatically scolling and gets in the way of reading and typing. It is really annoying. Can someone tell me how to switch this off. Thanks again
Lucky Patcher has a "clear cache" option. Maybe try that? Should force all the Android apps to optimize at boot and maybe fix your issues.
Hello BullGawd,
I already tried that. I also tried going into Settings/App Manager and clearing the cache for Google Services Framework.
I even tried by pressing the small reset botton on the face of the head unit. I am trying to avoid doing a factory reset from the recovery screen.
Has anyone had this issue with this these head units? How did you get this error fixed.
Thanks,
ggee
Hi guys,
My unit is stock. But I think I am just going to flash a newer version of the factory firmware (kitkat 4.4.4). In the old threads there used to be two repositories. One was the huifei-fileserver, and the other was a Google Drive site. Now I only see the huifei-fileserver.
Anyways, I downloaded the latest KLD RK3188 800x480 firmware:
http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/
However, it looks like the firmware .img file is made up of two parts. Both are zip files and each one contains a .img file.
-Am I supposed to merge both of these files into one .img file? If so, how do I do this?
-Or am I supposed to put both of these .img files into the root of the sd card (then insert to the gps slot)?
I know how to flash and update the firmware. However, I have only ever seen this process done using one .img file - not two. Can someone please clarify what to do with these two files in order to flash them properly. I do not want to gamble and brick my unit.
Thanks,
ggee
is one an mcu.img file? If so, remote that and only flash update.img
Dave
TT_Vert said:
is one an mcu.img file? If so, remote that and only flash update.img
Click to expand...
Click to collapse
Hello,
The first zip file says Part1 and its 204MB in size. This zip contains one update.img (634MB when extracted). The second zip file says Part2 and its 91MB in size. This zip also contains one update.img (yet it is the same size when extracted - 634MB). This is confusing and should be something easy and straight forward.
I am not sure if both of these files need to be merged. If they are supposed to be merged, how would you do this (what app does this).
-OR-
I am not sure if both update.img files need to be copied to the root of the sd card. However, both files cannot have the same name within the same directory, otherwise one file will overwrite the other. One file name will need to be changed. But I believe once you change the name, the head unit will not recognize it as a firmware image anymore.
Can someone please clarify this.
Thanks,
ggee
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
TT_Vert said:
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
Click to expand...
Click to collapse
Hello,
Yes, these are winrar files and I also use the winrar software. Sorry, I tend to use the word "zip" when talking about compressed file formats in general. Both files I am speaking about are winrar (Part1 and Part2). And each has an update.img file. How do I combine the files? Is there a special function within winrar?
BTW - do you have any idea about my original problem (google services stopped working)? Since I have not gotten a definitive answer, I was thinking about either doing a factory resetting, or just updating the firmware and mcu. I decided to update and that is why I'm stuck on these two "winrar" files, and how to combine them.
Thanks,
ggee
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Dave
TT_Vert said:
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Click to expand...
Click to collapse
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
There is no fix but myself and another person did try a bunch of different versions so search for it to find the most stable version.
gguevara said:
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
Click to expand...
Click to collapse
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
vinpee said:
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Click to expand...
Click to collapse
sciux said:
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello guys,
Yes. I was able to correct the problem.
All I did was re-flash the stock firmware rom. You can either re-flash your current version (if you have the update.img file for your head unit model). Or you can find the post in the Android Auto forum that lists most of the stock firmware roms. Make sure you select and download the correct one for your head unit type and model. I simply went back to the seller and asked them to send me the latest official stock firmware rom.
If you have certain apps and setting that you want to keep, make sure you make a back up before re-flashing the rom. Otherwise you will have to reinstall the apps and setting. Since I am basically keeping my head unit in a stock status (except for normal root), I just skipped the back up step and re-flashed the rom.
Extract the .zip or .rar of the firmware rom image. Then copy it to an SD card and insert it into you head unit. Reboot the head unit into recovery mode. Make sure to clear caches while you are in the recover mode, before re-flashing the rom. Then follow the menus for flashing the rom.
Later,
ggee