My phone after installed the android rom..all things run well...
but...only the power button works but not others...it may be due to different model of a Hong Kong Phone from Europe/ US phone...anyway to give the keys back functions that they should have? thanks
Go to Spare Parts, and change the power key to home.
You should search first... Thx. Also, post in the ROM/Build thread!! That way we know what you're using, instead of having to guess...
Yes, I searched, peoples using spare part as well... but I just seen End button behaviour only in Spare Parts...no other keys...so I wonder whether there is any other methods.?
sorry for making such thread
waiwai567 said:
Yes, I searched, peoples using spare part as well... but I just seen End button behaviour only in Spare Parts...no other keys...so I wonder whether there is any other methods.?
sorry for making such thread
Click to expand...
Click to collapse
Oh, I thought you only wanted to change the end call key.
If you want to change around other buttons, you'll have to hack at the source. Depends on what you're running - on HaRET, you'd need to modify the keymaps in the rootfs. On NAND, I'm guessing the keymaps in /system/etc. Either way, this isn't something that's easily done nor recommended.
Maybe an app like this.
http://www.addictivetips.com/mobile/remap-reassign-your-android-devices-keys-with-buttonremapper/
wizardknight said:
Maybe an app like this.
Click to expand...
Click to collapse
Thanks, is that one support NAND?:good:
waiwai567 said:
Thanks, is that one support NAND?:good:
Click to expand...
Click to collapse
Well it does say, "As can be expected, the application requires complete root access, with a NAND unlocked device and complete, permanent write access to the system directory."
This is where you have to start to do a little research on your own.
wizardknight said:
Well it does say, "As can be expected, the application requires complete root access, with a NAND unlocked device and complete, permanent write access to the system directory."
This is where you have to start to do a little research on your own.
Click to expand...
Click to collapse
yes, thanks! it's my fault by only focusing the samsung galaxy stuffssorry
Related
Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
aray92 said:
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
+1 10chars
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Spyderekz said:
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Click to expand...
Click to collapse
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
Click to expand...
Click to collapse
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Am I the only one who's seeing the same trend here that happened in the movie "Anger Management"?
He's only asking "Who you are." LOL
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Woops. Meant to quote aray92, not you since he/she said only the apk must be removed.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
ht tp://forum.swype.com/showthread.php?2287-Unable-to-uncheck-uninstall-Swype-Swype-PreLoad-Production-Device
Click to expand...
Click to collapse
Thank you for the link. The Swype beta always crashed for me and now I know why. I removed the files and now Swype works. Thanks!
I agree, I want to be able to install the latest swype. If I recall correctly, couldn't they make it so we could uninstall? I think that's how it was with OG Evo custom roms.
It's been removed from mine from day one.
I thoroughly inspect my ROM for every instance of software that I don't want.
gspitman said:
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
Click to expand...
Click to collapse
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
nabbed said:
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
Click to expand...
Click to collapse
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
its not in my rom either
NewZJ said:
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
Click to expand...
Click to collapse
Done, agreed, done, may not play right, and maybe!
anyone got the new Swype beta? Haven't tried it out yet
I am new to the android OS and havent really done much in the field of development lately... I was a BASIC and VBASIC coder back in the day... but I was going through the files on my Verizon Galaxy S4 and in /dev/_properties_ I found something labeled "ro.boot.hardware[]qcomro.boot.debug_level[]0x4f4cro.boot.cp_debug_level []0x55FFro.boot.emmc_checksum[]3ro.boot.bootloader[]i545VRUEMK2ro.boot.nvdata_backup[]ro.boot.boot_recovery... and it goes on and on. Any information would be greatly appreciated
That's code.
If I change it will it do anything?
theshedcrew said:
If I change it will it do anything?
Click to expand...
Click to collapse
Why?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Just wondering
theshedcrew said:
Just wondering
Click to expand...
Click to collapse
Its not like its just a diary from samsung... Hard to read through because your text view seems to be showing line feeds as an undisplayable characters, that box thing, whatever you want to call it.
But yeah that is one of your system files, that is data the OS uses. If you change it it will most likely just break what every thing you change from being specific code/information to random gibberish.
Just looked up the file... Thats not just a plain text file that is interpreted by the OS. I think you would have to get the source code to make changes then compile your own version.
Thanks. Like I stated above, its been a long time since ive coded (BASIC) and coding and development has come a long way since then
Use hex editor or you'll corrupt the file
theshedcrew said:
If I change it will it do anything?
Click to expand...
Click to collapse
Don't just open I with 'generic editor' and modify it and expect your device to boot properly. Use a GOOD hex editor from market and modify the values to retain proper structure or you'll regret it. You can be brave and add props not in use BUT they must present in the device for that to work. You can accomplish a lot in that file though or soft brick your device.
Yeah, I wouldn't just edit a piece of code just for the sake of editing code. Might mess your phone up.
Hi I'm new to XDA but I've used plenty of stuff from XDA in the past...
Yesterday I had and idea that only XDA Developers could fulfill: Make all of android UI VR...I'm no developer but I don't think it wouldn't be too hard to split the screen of a phone and project 2 small versions on either side of the display of what the screen would look like if it was full. But when you put on Cardboard all you would be able to see is a massive android screen in front of you. Also there is an xposed module called one handed mode where the ui gets shrunk to a portion on the screen... If this is possible shrinking it a bit more and projecting the image twice can't be hard. To navigate this interface you could use a Bluetooth/otg keyboard/mouse. Let me know what you think. To do this I'm guessing you would need root access. Let me know what you think and if you CAN make such an app please do and tell me about it.
hsa1907 said:
... To do this I'm guessing you would need root access.
Click to expand...
Click to collapse
Well allow me to clear this up, this is Xposed we are talking about, and basically to use Xposed you need root access... and I'm pretty sure that you are posting this in the wrong section mate.
nikctsh said:
Well allow me to clear this up, this is Xposed we are talking about, and basically to use Xposed you need root access... and I'm pretty sure that you are posting this in the wrong section mate.
Click to expand...
Click to collapse
Where would you recommend I post it
hsa1907 said:
Where would you recommend I post it
Click to expand...
Click to collapse
Check out the sticky notes and you will have your answer
nikctsh said:
Check out the sticky notes and you will have your answer
Click to expand...
Click to collapse
What do you mean sticky notes??
There was a need to record conversations on Android. I read about it, and after much experimentation came to the conclusion that the standard means of recording quality does not work or does not work on many phones. It should be written as a library and through the use of root rights. How do I not found. Maybe there is someone developments or links to projects?
koljsch.work said:
There was a need to record conversations on Android. I read about it, and after much experimentation came to the conclusion that the standard means of recording quality does not work or does not work on many phones. It should be written as a library and through the use of root rights. How do I not found. Maybe there is someone developments or links to projects?
Click to expand...
Click to collapse
There are a few things around the site about it but most either disable it or its not part of the stock os. This is due to legal reasons as recording phones calls is not legal in many areas and without a warrant never admissible in court.
You may have to program it into your os to get it to work right.
You may have to program it into your os to get it to work right.
Click to expand...
Click to collapse
But many applications is realized through Native library where recording is not supported. I am wondering whether there is a library in the public domain, or information on how to enable support in the OS?
koljsch.work said:
But many applications is realized through Native library where recording is not supported. I am wondering whether there is a library in the public domain, or information on how to enable support in the OS?
Click to expand...
Click to collapse
So have it built in. Alot of apps I have tested (legal reasons) have not worked at all. Some apps try to use root xploits to make it happen.
Some apps try to use root xploits to make it happen.
Click to expand...
Click to collapse
Exactly! There is information on how I can implement it in your own application?
koljsch.work said:
Exactly! There is information on how I can implement it in your own application?
Click to expand...
Click to collapse
I'm sure there is somewhere in the Google docs and how tos. It will most likely be ripping an app apart to see how they try to do it and then trying to make your own. Most apps have given up due to the security nature of it.
I'm sure there is somewhere in the Google docs and how tos.
Click to expand...
Click to collapse
Unfortunately, I am looking for information on this issue for a long time and found nothing. I would make specific reference, if any. He read a bunch of articles, he also tried a bunch of options, but about change through Ruth nowhere information.
koljsch.work said:
Unfortunately, I am looking for information on this issue for a long time and found nothing. I would make specific reference, if any. He read a bunch of articles, he also tried a bunch of options, but about change through Ruth nowhere information.
Click to expand...
Click to collapse
Might want to start here.
https://code.google.com/p/call-recorder-for-android/
https://www.google.com/search?q=how...spvd=1&ie=UTF-8#q=call+recording+android+code
Might want to start here.
Click to expand...
Click to collapse
The first link without root.
The Google naturally searched all examples without root.