I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you
xtrezpasor said:
I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you
Click to expand...
Click to collapse
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.
I signed into my google account and google voice "just worked". Of course i can't make any calls but i can use it to send texts and receive texts sent to my gv number.
Sent from my LogicPD Zoom2 using XDA App
I think if you could lift the data/configuration from your existing phone then you could copy that to the Nook and be working. I could not find where the data was stored though for the app.
GarJones27 said:
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.
Click to expand...
Click to collapse
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.
KitF said:
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.
Click to expand...
Click to collapse
Can you give a short tutorial on how to get this set up? I too (and im sure others) would like to be able to text from the Nook.
Sent from my HERO200 using XDA App
Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.
seeddemon said:
Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.
Click to expand...
Click to collapse
Edit: Okay, set up Google voice and I'm able to send texts using that number however the apps that require a phone number do not see it. Not a huge deal, but there might be more apps out there that require a phone number to work.
I simply set up Google voice via the Google.com/voice website. And then got a Google number to use for texts. In the voice app you can compose a message and my Google contacts are available.
Sent from my Nook Color.
This isnt what what I was looking for - I was looking for a way to use verizon Fios manager...
hijacked
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?
3EyedPhish said:
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?
Click to expand...
Click to collapse
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.
DizzyDen said:
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.
Click to expand...
Click to collapse
I got the FIOS app to run on my Nook by doing the reverse of this. I found the few places in the app where the phone number was looked up and replaced those by calls to get an apps prefs setting "Display Name" which is entered during set up but unused by the app. So I put in the phone number under Display Name during set up.
This was done using apktool to patch the app but I am reluctant to post the modified version as this is explicitly ruled out by license agreement.
I did consider going the TelephonyManager route but as I am using CM9 which is still changing quite a bit then that becomes a moving target. If CM9 puts explicit coded support in for entering a number like CM7 did then that would be the best option. I did find, however, when using the CM7 option that it had a tendency to lose the entered number during reboots.
You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.
mateorod said:
You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.
Click to expand...
Click to collapse
That looks like a better more general method. In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.
It is a pretty neat program, with a ton of functions and uses that go pretty unnoticed.
One note, though: due to an update in the CM repo, our auto-patcher ( and even the patches I used to make the auto-patcher) broke.
I have updated everything for CM9, but we are waiting on an aokp build before releasing another version of the auto-patcher.
But the Botbrew packages are up to date and can be used immediately for 5/08 and the patcher will be updated soon.
If you are running an older build, make sure the package you use matches the build date. And the auto-patcher still works to builds from 5/06 and earlier.
bobtidey said:
In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.
Click to expand...
Click to collapse
I tried out the new version of the Verizon app and it now does allow use of a 4 digit PIN as opposed to a phone number for setting up the remote control pairing. It finds the set top box OK but then immediately crashes on the Nook Color CM9.
I'm going to do a bit more investigation and maybe try it from a Touchpad to see if that behaves the same way.
Related
I have seen few apps that are capable of doing this over Wi-Fi, Bluetooth and USB. But I am more interested in something that can do it over 3G. At work my desktop PC is not on a wireless network; there is Wi-Fi but on a spate subnet with no easy access to the main network. I do have Bluetooth / USB on my main desktop but I work from different PCs therefore its not very convenient for me to pair/connect it each time I go to a different PC. And I don’t use Wi-Fi at home either.
Then there are other benifits to using 3G like I can still access the phone even if I forget it somewhere (i.e at home in the car etc). The new HTC Sense services for HTC Desire HD will have remote access to SMS, call and location information , which is exactly what I'm after. But for now SMS alone is enough.
I came across one App called SMS2PC which can connect to a computer over 3G. But from what I gathered, with that the phone connects to the PC and pushes notifications, not the other way around. This is not going to work for me because at work I am behind a corporate firewall, so my phone cannot access the desktop.
Any other solutions ??
EDIT : i know SMS backup can backup text messages to google, but I can't reply from there. So that wont help much. And I'm not in US, therefore I dont have access to Google Voice service, so replying through that is not going to work either.
Is Google Voice avilable to you (specifically, you will need a Google Voice phone number)? If so, that will be my recommendation. In addition to free SMS and visual voice mail, you can use your Google Voice anywhere that you have access to a web browser. It doesn't have to be your phone.
foxbat121 said:
Is Google Voice avilable to you (specifically, you will need a Google Voice phone number)? If so, that will be my recommendation. In addition to free SMS and visual voice mail, you can use your Google Voice anywhere that you have access to a web browser. It doesn't have to be your phone.
Click to expand...
Click to collapse
No google voice is not available ( as mentioned in my last line , coz I knew some one would suggest that).
I wonder why no one has made such an app so far.
Maybe I'll have to write my own.. haven't done any android programing yet, guess its about the time.. waiting for a break from work to start playing around with it a bit...
PhoenixFx said:
I have seen few apps that are capable of doing this over Wi-Fi, Bluetooth and USB. But I am more interested in something that can do it over 3G. At work my desktop PC is not on a wireless network; there is Wi-Fi but on a spate subnet with no easy access to the main network. I do have Bluetooth / USB on my main desktop but I work from different PCs therefore its not very convenient for me to pair/connect it each time I go to a different PC. And I don’t use Wi-Fi at home either.
Then there are other benifits to using 3G like I can still access the phone even if I forget it somewhere (i.e at home in the car etc). The new HTC Sense services for HTC Desire HD will have remote access to SMS, call and location information , which is exactly what I'm after. But for now SMS alone is enough.
I came across one App called SMS2PC which can connect to a computer over 3G. But from what I gathered, with that the phone connects to the PC and pushes notifications, not the other way around. This is not going to work for me because at work I am behind a corporate firewall, so my phone cannot access the desktop.
Any other solutions ??
EDIT : i know SMS backup can backup text messages to google, but I can't reply from there. So that wont help much. And I'm not in US, therefore I dont have access to Google Voice service, so replying through that is not going to work either.
Click to expand...
Click to collapse
I use smstools. It is in every major repo. However - from your non-technical wording - I assume that you use the gamerz OS (Windos). Worry not, you can easily compile the program yourself, or google for binaries.
HelloH said:
I use smstools. It is in every major repo. However - from your non-technical wording - I assume that you use the gamerz OS (Windos). Worry not, you can easily compile the program yourself, or google for binaries.
Click to expand...
Click to collapse
Yes, I use Windows mostly . Thanks for that link, but I don't think thats quite what I want either. That seems to use the phone as a modem to send and receive SMSs; which means I'll have to connect the phone to a PC locally (i.e USB, IR, BT etc..).
I'm looking for a solution that allows me to connect to the phone remotely over the internet (phone online on 3G) to access and send messages. A setup where there is a PC client which polls the phone periodically for new messages and a server running on the phone allowing the PC client to gain access to its messaging service. So I don't have to connect/disconnect every time when changing PCs, it will also allow me to connect even when the phone is not with me (left behind at home / car ).
Ah, I got it now!
Well, of course you could compile SMSTOOLS for your phone
Or take a look at RemoteSMS or similar apps!
Also possible to remote control your handset via vnc-server. That one has far more possibilities than remote SMS-ing...
HelloH said:
Ah, I got it now!
Well, of course you could compile SMSTOOLS for your phone
Click to expand...
Click to collapse
I’m coming from Windows development side, so pardon me for my ignorance on Linux dev. But from the little I know, you can't compile Unix/C code to Android, am I wrong ? At least not in a straightforward manner... You can only develop apps using their customized Java (Dalvic) , right
Even if its possible, I think developing an app from ground up is far more easier than trying to integrate smstools in to android. Besides, that doesn't solve my problem at all, because accessing the phone from the PC is the issue, and I don't see how running smstools on the phone is going to solve that.
HelloH said:
Or take a look at RemoteSMS or similar apps!
Also possible to remote control your handset via vnc-server. That one has far more possibilities than remote SMS-ing...
Click to expand...
Click to collapse
RemoteSMS only works over Wi-Fi and BT, no 3G support .
I guess remote desktop is one solution, but I prefer a much simpler app. Besides VNC will not send me any notifications, I have to manually check. ..
Looks like I'll have to write my own app for this . Havent done any android development yet, looks like this is going to be my first project..
Wifi Keyboard works on 3g (yes dumb but )
3G might be blocked by some carriers.
Click to expand...
Click to collapse
So it's means it can be used over 3G
PhoenixFx said:
IAnd I'm not in US, therefore I dont have access to Google Voice service, so replying through that is not going to work either.
Click to expand...
Click to collapse
You don't need to be in the US to get a Google Voice account or use it for SMS. I am in Canada and use it for SMS all the time.
See this link. Note that despite the title this will work for any country.
http://www.wifitalk.ca/iphone/howto-google-voice-in-canada/
brunes said:
You don't need to be in the US to get a Google Voice account or use it for SMS. I am in Canada and use it for SMS all the time.
See this link. Note that despite the title this will work for any country.
http://www.wifitalk.ca/iphone/howto-google-voice-in-canada/
Click to expand...
Click to collapse
Thanks, I'll give it a try. Are SMSs free for international numbers as well ?
EDIT : I don't want to login through some unknown proxy server and give out my credentials. Besides, it is not a permanent solution. another dead end
Waiting for new ideas
exadeci said:
Wifi Keyboard works on 3g (yes dumb but )
Click to expand...
Click to collapse
PhoenixFx said:
Waiting for new ideas
Click to expand...
Click to collapse
Hum ..... Have you tried it ?
PhoenixFx said:
I’m coming from Windows development side, so pardon me for my ignorance on Linux dev. But from the little I know, you can't compile Unix/C code to Android, am I wrong ? At least not in a straightforward manner... You can only develop apps using their customized Java (Dalvic) , right
Click to expand...
Click to collapse
Linux is a kernel, and Android is a Linux kernel based operating system. You can compile anything (that compiles for GNU/Linux for the given architecture) for Android/Linux as well. It will be native code however (as opposed to DALVIK, which is VM code). You have the option to cross-compile on your PC, or to compile code right on your phone. It is a command line affair... not some nice one-click task.
BTW I did not see in their own advert, that RemoteSMS would be limited to wifi... you sure? (Would be pretty weird move from them, since communicating over wifi and 3G is not really different from the programmer's point of view)
Found this today , posted on XDA : talkmyphone.
Exacly what I was looking for .
YAY!
Thank you! I have been looking for something like this because I am also behind a corporate firewall at work.
OK, I'm frustrated.
I have been trying to add my gtab to my devices on the new Market site, and have so far been unable to do so. Actually, that is not exactly true. I can get it to show up partially.
I have a Droid phone, and I see the phone when I go to my Market Account, Settings, My Devices. I enter the new nickname for my tablet.. [tablet, gtablet, Viewsonic G-Tablet, Malata ... all tried separately], I check the "show in menus" option. Press the Update button on the right. And nothing happens. The Maker, Model, Carrier columns for the tablet are empty, with only a hyphen. I cannot enter information directly into these columns, and whenever I try to download something, only the phone shows up. When I click on the little black triangle to expand the devices, I DO see the GTablet there. But it is grayed out with a question mark beside it. It says it is not compatible with this device. Every single app is not compatible with my tablet?
What am I missing?
Full Market fix
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044
Ya funny thing is, I think mine showed up (and someone will correct me I bet) as VS GTablet Advent Vegan 5.1.
Something like that but I thought oh they even know I am running the VEGAn ROM. Interesting indeed.
i'm runing vega5.1 and i had to do nothing... he just appeared..
but yesterday i had to do the market fix again and it disappeared.. LOL
weird
tysonkam said:
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044
Click to expand...
Click to collapse
my build.prop is correct and does not appear on market...
like i said before, it appeared then after fixing market again it does not
Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.
tedlogan42 said:
Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.
Click to expand...
Click to collapse
I had the EXACT same thing happen to me. It was there as a malata gtab running tnt lite, and I had to do market fix again. Now its like it was never there. Is there anyone we can talk to at google about this? Like a customer support type?
Sent from my GTablet-TnT-Lite using Tapatalk
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Agree
Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
+1 I just use the market on the tablet.... My device(for now) is showing in web market.
My G-Tab running Vegan 5.1 is working in the new market with no changes or modifications except editing the nickname. I installed an app to it via the new market already. Since I have a Droid also, I kinda like the ability to install on either or both devices. YMMV, apparently...
Nvidia VEGAn-TAB-v1.0.0B5.1
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications. Since I wasn't connected to the internet at the time it was held in abeyance. Once I got a wifi connection, boom down they came. So I can now peruse the market at work or as I monitor these forums, find an application, purchase it (or not) while I am still thinking about it and have it update the tablet the next time it connects. Not bad functionality for someone like me whose work environment is wifi restricted.
I still have one issue I would like to see Google fix. I purchased a application under one gmail account but after reflashing from tnt-lite to Vegan Tab I put my other account on the device first. Now I can't update that application without some tricky effort. Not sure I want to go through that effort or pay the $5 again
While that was me being stupid, I proposed to Google that I could envision the case where I might want to purchase an application with my work credit card and put that on their tablet and also purchase an application with my personal credit card. Their current schema doesn't allow for that. I can see where with telephones it might be a little more personal but tablets may start becoming shared devices say within a family.
What they seem to have for that situation is the ability to use more than one CC with the account. In that case you could use your work CC for some and personal for others.
Not a help for your situation, but it does address the situation you proposed.
Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Google has prerequisites that must be met for a device to have official and supported Market. GPS and cellular radio are on that list if I'm not mistaken.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.1 w/ Clemsyn's Kernel using Tapatalk Pro
anjenaire said:
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications.
Click to expand...
Click to collapse
I'm getting the same showing up in my market access, but where we differ, is I have yet to have an application actually download to my tablet. I've gone through 5-6 different apps that did show the G-Tablet as a compatible device, and these were not installed on my tablet before going to the web market...
The big difference now is I am seeing lots more apps using the legacy Market app on the tablet.
I figured the first week or so would be pounding the web market, and things seem to be settling down, if just a small bit.
Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.
So far my tablet is showing on the new market and allows me to download apps to it. I'm running vegan tab 5.1 if that helps anyone...
Sprdtyf350 said:
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.
Click to expand...
Click to collapse
You are probably right, i tend to lean towards everything being based on how these companies can make the most money. Like if what i said is true, maybe then google gets a bigger kick back from the carriers, or phone manufacterers. Its ATT 's fault really, lmao, since everything they do is based on getting more money from me as a subscriber. it seems loke they try to make evry feature, an extra charge, without lowering the standard monthly fees. (i know i am most likely wrong, it just seems this way to me). I am not askin for free stuff, it just seems like they keep the services i want out of my pockets' reach.
Sent from my GTablet-TnT-Lite using Tapatalk
Web market woes
I can confirm web market was working running TNT Lite... stopped working after redoing market fix. Web market working again... after flashing Vegan and wiping data.
For the people with working web based market: did you change your android id? if you did, did you change it to a different devices id or did you use one from an emulator?
Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom
What's the error, logcat ?, what's the app?
dude u gotta give some info if need a solution.
There could be a million things that could cause problems like that.
x2002dude said:
Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom
Click to expand...
Click to collapse
We are all waiting for an answer. I have an outstanding request in with Google that I have had to update several times as they seem to be dancing around the question. When and if I hear I will post a response.
The App is "The Going to Bed Book" or "PopOut! The Tale of Peter Rabbit" - Our users are getting a "Invalid License" error. We're going to root one of our nooks soon to do some testing, but until then we were thinking we might be able to get something from the forums. Both users who reported the issue were running CM7, which I also run on my HTC IS, and runs our apps fine. Thus we're thinking it could have something to do with the device ID running against the licenses?
As we set up restrictions by device, We were curious what a rooted NC running CM7 would show as in terms of a device on the Android Market place?
Thanks for the help guys, and thanks for the patience. I'm not the actual Android developer on the team. He's out of the office for the week,
Cheers,
Tom
I think he means he is having trouble getting the application to install from the market in general. I looked up the applications and the NC was not a supported device.
I don't want to pay the money to download it to my phone and sideload it (I'm at work anyways). I don't know much about applications and how devices are determined to be compatible other than maybe their permissions. However, these applications (there are two on the market), don't require anything other than SD access.
As we set up restrictions by device....
Click to expand...
Click to collapse
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?
model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.
patruns said:
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?
Click to expand...
Click to collapse
No, this feature is available to every developer since a long time. but there are 600 or so devices so not a lot of people bother with it.
rigy73 said:
model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.
Click to expand...
Click to collapse
Actually, questions to the market run against your account and the email info and log the following device details:
> IIILanguage: en
> IssueType: market_website
> Language: en
> android_app_name: Facebook
> android_os: gingerbread
> android_os_other:
> device_manufacturer: other
> device_manufacturer_other: Barnes & Noble
> hidden_country: US
> website_issue_select: grayed_device
device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.
rigy73 said:
device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.
Click to expand...
Click to collapse
Those were direct quotes from what Google's filters picked up when I sent an email while logged in to the market.
Thanks guys, this will be a good start. If and when we resolve the issue I'll be sure to post an update with the details. I really wish Android Market supported promo codes; we'd love to be able to throw out some free copies for you guys to have a look at and test for these one off issues.
Thanks Again!
I assume if you sideload the .apk it will install fine?
Just want to contribute that I have the Going to Bed Book installed and running fine on my Nook. I am still running CM7 7.1RC, and have my build.prop spoofed for Netflix (no longer required, but I never changed it back and haven't flashed a new CM7 in a while). The only change I made in build.prop was setting the manufacturer to HTC.
The book runs great and is my son's new favorite app.
You may have an issue using get.DeviceID()... have one of your users use my IMEI generator and see if it fixes their problem. They can also spoof Manufacture, Device and Model with the newest version.
IMEI Generator Thread.
I have it on my CM7 (7.0.3 to lazy to update, running off sd no changes to build.prop) Nook and it works fine. My daughter loves it.
Some of the pages are kind of hard to register a turn, and it always starts upsidedown then flips itself over. But both of those things are the same on my incredible 2 as well.
Sent from my ADR6350 using XDA App
Hi Guys, the browser hack that wipes Samsung phones is not limited to just those handsets. These guys do a better job of describing the whole thing:
http://www.theverge.com/2012/9/26/3412432/samsung-touchwiz-remote-wipe-vulnerability-android-dialer
Here is a direct link to the exploit test:
http://dylanreeve.com/phone.php
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Maybe people can post D3 Roms that aren't vulnerable.
majatt said:
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Click to expand...
Click to collapse
Also, installing DialerOne and making it the default will protect you as well - you do not have to leave it without a default dialer set. DialerOne is actually a good dialer - I used to use it with my Droid Eris with CyanogenMod ROMs, in order to have the dial by name function that the Sense dialer supported back. And you can still leave the stock dialer set in a home page or on the launcher dock - it will still work if you call it up. It will not be called up if you launch the dialer from another app, though, if you make DialerOne the default.
The stock dialer is vulnerable - a predictable result, based on the vulnerability of MavRom, but I did want to say that I tested it. I haven't tested any other ROM - at this point, I don't have much time to try some out, and I think I recently deleted my most recent Liberty and Bionic Nandroid backups.
Let's see how long before Moto releases a critical patch update for stock.
Thanks, this is good to know. I thought it was only Samsung phones that had the issue, but since I'm still on stock 2.3.4 it appears I'm vulnerable. I have GrooveIP Lite installed on my phone, an app that allows you to make voice calls with using your Google Voice number. With this app installed I get a complete action using Dialer or GrooveIP window so I should be safe if I get a random popup Ill be sure to not select Dialer.
I heard about this "wipe" problem and when I saw it was just passing dialer codes to the fone I knew it would affect more than just Samsung.
Does anyone know if they have a list started of fones that might be vulnerable?
I read somewhere (though haven't tested it...) that the D3 does not have a dialer code that resets the phone, as the Samsung phones do/did. So, the D3 fails the display the IMEI test, but I believe that the reset code does not work with the D3.
FYI: CM10 kexec isn't vulnerable. Probably b/c it's JB (I think they fixed the vulnerability in JB). I go to the site and dialer pops up w/ *#06# No IMEI displayed
Sent from my AOKP JB GT-P3113 using Tapatalk
8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.