Related
This Tablet Im looking at costs the same and has twice the features. Granted the processor isnt quite as strong. But wouldnt this have been a nice alternative to what I bought I think after christmas once I can save some money I might pick one of these babies up its called theKobo Vox. If anyone does pick one up as an alternative, Let me know how it runs I would like to know wether or not its worth it. I would post the link but It wont let me because I dont have that ability yet. Im working though trust me.
It has a slower processor, but it has an sd card slot. What are these other features that the Fire lacks?
Was just looking at specs and think I would rather stay with the kindle fire
Sent from my Kindle Fire using Tapatalk
victimofcanada said:
This Tablet Im looking at costs the same and has twice the features. Granted the processor isnt quite as strong. But wouldnt this have been a nice alternative to what I bought I think after christmas once I can save some money I might pick one of these babies up its called theKobo Vox. If anyone does pick one up as an alternative, Let me know how it runs I would like to know wether or not its worth it. I would post the link but It wont let me because I dont have that ability yet. Im working though trust me.
Click to expand...
Click to collapse
How is the kobo vox better than the nook color (which at least has a small developer community)?
Don't get me wrong, I would like to see kobo/borders succeed (ie I was at some point interested in buying one of their eInk readers), but the kobo vox (like the eInk device I was interested in) was too little too late.
12 months ago the Kobo Vox might have had a chance ... now though?
Nook Tablet cant even get kexec because they have a locked and signed bootloader. Meaning no chance for custom kernels or a way to load a custom kernel on top of the standard one. The Kobo Vox has volume buttons. which is nice. easier recovery navigation/button combos
grvthang said:
It has a slower processor, but it has an sd card slot. What are these other features that the Fire lacks?
Click to expand...
Click to collapse
It also has a camera and It seems to have volume buttons also physical navigation menu.
death2all110 said:
Nook Tablet cant even get kexec because they have a locked and signed bootloader. Meaning no chance for custom kernels or a way to load a custom kernel on top of the standard one. The Kobo Vox has volume buttons. which is nice. easier recovery navigation/button combos
Click to expand...
Click to collapse
andTab said:
How is the kobo vox better than the nook color (which at least has a small developer community)?
Don't get me wrong, I would like to see kobo/borders succeed (ie I was at some point interested in buying one of their eInk readers), but the kobo vox (like the eInk device I was interested in) was too little too late.
12 months ago the Kobo Vox might have had a chance ... now though?
Click to expand...
Click to collapse
The VOX already has hardware features that the kindle and nook are both lacking. Also, it is running almost clean android so its a familiar interface we all know. Granted if this tablet survives (which I hope it does) The next logical step would be huge updates to the processor and ram in the device. while the nook and kindle both would have minor adjustments to the processor and ram and adding features that should have been included in the initial release. I do love my Kindle don't get me wrong I feel like the community here can do some great things with it but its just lacking some major features and Amazon came on a little apple-esque with it. It felt like if there was no root it was almost entirely proprietary.
victimofcanada said:
It also has a camera and It seems to have volume buttons also physical navigation menu.
The VOX already has hardware features that the kindle and nook are both lacking. Also, it is running almost clean android so its a familiar interface we all know. Granted if this tablet survives (which I hope it does) The next logical step would be huge updates to the processor and ram in the device. while the nook and kindle both would have minor adjustments to the processor and ram and adding features that should have been included in the initial release. I do love my Kindle don't get me wrong I feel like the community here can do some great things with it but its just lacking some major features and Amazon came on a little apple-esque with it. It felt like if there was no root it was almost entirely proprietary.
Click to expand...
Click to collapse
Reading comprehension = zero.
It is essentially the SAME HARDWARE as the Nook COLOR!!!!!! But without a dev community.
Too little, too late.
I think the biggest advantage the Fire has over this device (and many others) is the sheer number of them on the market.
Many of the (real, lol) developers I know are getting orders for applications directed at the Fire. With the amount of market segmentation for android devices, finding a 'target' is a big deal for people.
andTab said:
Reading comprehension = zero.
It is essentially the SAME HARDWARE as the Nook COLOR!!!!!! But without a dev community.
Too little, too late.
Click to expand...
Click to collapse
Only way to get a nook color outside the US is importing it afaik
This is the same price (against the price charged by an importer) and you can just buy it on the high street (UK).
unrandomsam said:
Only way to get a nook color outside the US is importing it afaik
This is the same price (against the price charged by an importer) and you can just buy it on the high street (UK).
Click to expand...
Click to collapse
Which still proves my point: same price, same hardware but no dev community.
And the OP seems to be from Canada ... where he can get the Nook Color for $150 or less (depending on the available deals).
I've exchanged several PMs with pokey9000 today. He has taken a look at the software update packages for both the 2nd generation KF and the 7" HD. The MLO (xloader, 1st stage bootloader) is signed and the boot header is the type used for HS (high security) OMAP devices with the M-Shield turned on. If the setup is comparable to the Nook Tablet, this is not good news for those hoping to modify these devices in one way or another. The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Some clarification... and much left unanswered...
kinfauns said:
The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
Click to expand...
Click to collapse
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence). If you're curious, you can look at the CyanoBoot 2nd bootloader for NT description or source to see what's going on.
I've taken a VERY quick look at the bootloader source for the HD7 as well, pushed here for anyone who wants it. There is in fact signature verification code in the uboot source (~line 140).
Also, looks like there are three configs-- bowser, jem, and tate. I have to look at it closer but it looks like tate is a subtype of bowser, and the HD7 I assume is tate. Hashcode also found a "radley" in the kernel code, but I haven't looked at that.
Anyway.. it is possible that bauwks' flaw or some other flaw exists in this signature verification code, but the code isn't identical to NT so who knows.
Incidentally, the new revision of the Kindle Fire (otter2) also has the same code, and there's a thread about the signature issue here as well.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Click to expand...
Click to collapse
Yeah.. it all depends on whether there's a flaw as there was with the Nook Tablet... someone get bauwks on the line
Meanwhile, I'm enjoying my free (as in speech) Nexus 7...
fattire said:
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence).
Click to expand...
Click to collapse
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time. Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Meanwhile, I'm enjoying my free (as in speech) Nexus 7...
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 7 using xda premium
fattire said:
Not quite right. NT's exploit was far more complicated than that and has nothing to do with using the external SD card (or depending on one). It could have been done simply with root (or any other method for overwriting a partition, which was required to insert a 2nd unsigned bootloader into the boot sequence). If you're curious, you can look at the CyanoBoot 2nd bootloader for NT description or source to see what's going on.
...
Click to expand...
Click to collapse
Thanks for the clarification and your input as well. I just wanted to get the discussions going on the possibilities of opening up this device to development, but also temper some expectations. There are many people waiting and some undoubtedly have ordered with the assumption that these 2nd generation devices will be getting the full range of development enjoyed by the original. I was mostly paraphrasing and summarizing, so I'll leave the details to those with the know-how.
I'm sure many people will be scouring the code and tinkering with their new devices in the coming days to figure something out.
Boring stuff...
pokey9000 said:
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time
Click to expand...
Click to collapse
It's not THAT risky, I don't think. Even w/o SD card on NT, the safe(st) way to do it would be to replace the recovery partition with a 2ndboot/cyanoboot-enhanced recovery.img from a normal rooted boot. If recovery fails, you're still okay-- you can always just boot normally, gain root, and replace recovery again. If you're verified good, then use recovery to replace boot.img.
On NT, the normal secure boot sequence is unaffected when you replace recovery. That's because on the NT, you are never removing or touching the original uboot (ub1), so there's not much danger of a brick as long as you always have two means for booting (normal + recovery).
This is all academic as far as KFire HD goes, as I'm guessing from existence of the "crypto" partition that bauwks' bugfix won't work. I need to give a look at the signature verification stuff, as I haven't looked at it yet, but I'm not particularly optimistic.
pokey9000 said:
Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Click to expand...
Click to collapse
True, although w/NT, BN can only patch it by modifying the hardware, which would create massive support headaches for two versions of the boot. This is because w/unchanged hardware, the current, signed xloader->ub1->ub2 chain can always be used to load whatever. Again, I have more clarification on this-- if you're not already familiar with the details, find me on IRC.
speaking of fastboot, apparently if CONFIG_MACH_BOWSER_SUBTYPE_TATE is set, fastboot_idme is defined and fastboot and other debugging stuff seems to be turned on. I'm pretty sure "idme" is a uboot command. It's commented-out of drivers/fastboot.c as a shortcut to be enabled for TATE only.
FWIW, here are some various versions of the bowser board:
Bowser-Jem-PreEVT2-
Bowser-Jem-PreEVT2-
Bowser-Tate-PreEVT2.1-
Bowser-Tate-PostEVT2.1-
Bowser-Tate-PostEVT3HS2-
Bowser-Tate-DVT-
Bowser-Tate-PVT-
Bowser-Radley-
tate = product id 7
jem = product id 8
radley = product id 9
HS is High Security, I'm pretty sure.
Someone apparently is a fan of To Kill a Mockingbird (Boo Radley, Atticuls "Jem" Finch, Heck Tate, etc.). I don't know what the Bowser connection is... this guy? Or maybe just one of these.
Gotta go.
software RD of AMAZON said it was impossible to crack the NEW KF system, unless u know the key in the machine
This was probably done in response to all the bricked Kindle Fires that were returned with the original Fire. That and the fact that if they didn't, it probably would have meant a price increase due to increased warranty expense. However, it seems i would make sense to simply allow an owner to pay a small fee to unlock the boot loader and register a modified Fire as "no warranty" for software issues.
kinfauns said:
I've exchanged several PMs with pokey9000 today. He has taken a look at the software update packages for both the 2nd generation KF and the 7" HD. The MLO (xloader, 1st stage bootloader) is signed and the boot header is the type used for HS (high security) OMAP devices with the M-Shield turned on. If the setup is comparable to the Nook Tablet, this is not good news for those hoping to modify these devices in one way or another. The Nook Tablet's exploit was to utilize the external sdcard as an alternate boot device and that doesn't really help with these 2nd generation KFs.
It's all subject to verification by someone who has a device in hand, but it doesn't look good. This is not to say that it's impossible, but it will be considerably more difficult to manipulate these devices than their 1st generation cousin.
So, let's all hope for the best, but be prepared for the worst. If you plan to buy one of these devices, buy them as an Amazon tablet to be used in the Kindle Fire ecosystem. Don't buy them expecting to run Jelly Bean the day after tomorrow.
Click to expand...
Click to collapse
I got my 7" Fire HD in the mail yesterday and am in this 100% to see custom roms running on it.
While I have just under a year of Android tinkering under my belt and many more years of experience playing with pc's and various flavors of embedded systems, I dunno where it all begins for this new device, but I want to help the dev community in any way I can.
If anybody has specific requests about the device or needs to test out something on one, I don't mind being a guinea pig, as long as there isn't too much risk of bricking my cool new toy...
I will take a look at the u-boot sources of the new fires too and see how/what they have changed. Very possible that they fixed the funny flaw in the loading process for this iteration of their devices.
It would certainly be sad since a full HD android tab is tempting. At least for the 7inch category we have the nexus7 as an extremely good alternative.
Ifixit has a teardown of the device, and there is a big test point labeled "USB BOOT" on the main board, and two smaller ones labeled "RX" and "TX"....
http://guide-images.ifixit.net/igi/UapMeZFPXthjTrEn.huge
Returned
I have already hit the Return Item button on this. I could care less about the speakers and the screen! Gonna pick up the Nexus 7 instead.
pokey9000 said:
Technically true, but altering the boot chain with a removable microSD makes it a reversible process. Overwriting the boot image on emmc without any other boot options is serious brown trousers time. Now if they left in fastboot, then its not so scary if a similar hack to the NT can be done. Still, with no possibility of USB boot there's no recourse if any exploits get patched.
Yes.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
just wait for pokey9000 to answer ， wait for u have idea how to USB boot it
psomero said:
I got my 7" Fire HD in the mail yesterday and am in this 100% to see custom roms running on it.
While I have just under a year of Android tinkering under my belt and many more years of experience playing with pc's and various flavors of embedded systems, I dunno where it all begins for this new device, but I want to help the dev community in any way I can.
If anybody has specific requests about the device or needs to test out something on one, I don't mind being a guinea pig, as long as there isn't too much risk of bricking my cool new toy...
Click to expand...
Click to collapse
Well I for one will be quite happy if someone can get an alternate launcher to work without rooting. Didn't have to on the original KF for them to work.
---------- Post added at 12:50 PM ---------- Previous post was at 12:46 PM ----------
JaxDomino said:
I have already hit the Return Item button on this. I could care less about the speakers and the screen! Gonna pick up the Nexus 7 instead.
Click to expand...
Click to collapse
I hope not cause the Nexus 7 for those two things ain't as good as this Fire HD.
Worst case scenario, there's always the kexec option. As a last resort, it works even on devices where the bootloader was never cracked.
robertc88 said:
Well I for one will be quite happy if someone can get an alternate launcher to work without rooting..
Click to expand...
Click to collapse
Yes, that would do it for me too (along with some ability to sideload apps). I preordered the 8.9 HD so I'll keep close watch on the development. If no solution is found before end of November, I just might cancel, and look around for what's hot (and rootable) at that point.
bournezhang said:
just wait for pokey9000 to answer ， wait for u have idea how to USB boot it
Click to expand...
Click to collapse
USB boot needs a special boot loader (aboot in omap4boot used in Firekit) , and at least on the Nook Tablet it needs to be signed too. I doubt that TI's customers can or would opt for locking just flash boot so I'm going to assume that it won't work on the new Fires without a signed USB loader.
glad to see everyone brainstorming over here. sorry for the bad news. i'm gonna follow these closely as i want to get a kfire hd for the gf eventually, but only when this bootloader gets unlocked. til then, back over to my n7 (which i find boring at times, because everything just works... bummer) lol
fattire said:
It's not THAT risky, I don't think. Even w/o SD card on NT, the safe(st) way to do it would be to replace the recovery partition with a 2ndboot/cyanoboot-enhanced recovery.img from a normal rooted boot. If recovery fails, you're still okay-- you can always just boot normally, gain root, and replace recovery again. If you're verified good, then use recovery to replace boot.img.
On NT, the normal secure boot sequence is unaffected when you replace recovery. That's because on the NT, you are never removing or touching the original uboot (ub1), so there's not much danger of a brick as long as you always have two means for booting (normal + recovery).
This is all academic as far as KFire HD goes, as I'm guessing from existence of the "crypto" partition that bauwks' bugfix won't work. I need to give a look at the signature verification stuff, as I haven't looked at it yet, but I'm not particularly optimistic.
True, although w/NT, BN can only patch it by modifying the hardware, which would create massive support headaches for two versions of the boot. This is because w/unchanged hardware, the current, signed xloader->ub1->ub2 chain can always be used to load whatever. Again, I have more clarification on this-- if you're not already familiar with the details, find me on IRC.
speaking of fastboot, apparently if CONFIG_MACH_BOWSER_SUBTYPE_TATE is set, fastboot_idme is defined and fastboot and other debugging stuff seems to be turned on. I'm pretty sure "idme" is a uboot command. It's commented-out of drivers/fastboot.c as a shortcut to be enabled for TATE only.
FWIW, here are some various versions of the bowser board:
Bowser-Jem-PreEVT2-
Bowser-Jem-PreEVT2-
Bowser-Tate-PreEVT2.1-
Bowser-Tate-PostEVT2.1-
Bowser-Tate-PostEVT3HS2-
Bowser-Tate-DVT-
Bowser-Tate-PVT-
Bowser-Radley-
tate = product id 7
jem = product id 8
radley = product id 9
HS is High Security, I'm pretty sure.
Someone apparently is a fan of To Kill a Mockingbird (Boo Radley, Atticuls "Jem" Finch, Heck Tate, etc.). I don't know what the Bowser connection is... this guy? Or maybe just one of these.
Gotta go.
Click to expand...
Click to collapse
fattire is a beast for doing work on the Nooktablet with me, chm and all the other guys.... From what im reading, its actually kinda like booti from the Nook tablet. Very very interesting file at ./common/cmd_idme.c It seems as though theres a way to load a debugging kernel. Kinda curious if we can use that to smash a new boot into it. The following lines interest me:
./common/cmd_idme.c
Code:
#ifdef ENABLE_DIAG_KEY
if (!val_vol_up && val_vol_down) {
/* button up is pressed only */
printf("Tablet: Enter dkernel mode: ....\n");
*ptn = pdkernel;
}
Code:
case '2':
printf("Select Diagnostic image\n");
*ptn = pdkernel;
break;
and also this line in the ./include/config/tate.h
Code:
#define CONFIG_DIAGNOSTIC_BOOTCOMMAND "mmcinit 1;mmc 1 read 0x580 0x81000000 0x600000; bootm 0x81000000"
As for the boot hole that bauwks discovered on the nook tablet, it is not on this device, though it is highly possible that if this Diagnostic mode can be activated we can use the same exploit as we used with the fatload and the booti. This CONFIG_DIAGNOSTIC_BOOTCOMMAND can maybe do the same thing with something in the SAR memory, so its worth someone doing somemore research.
thebrave said:
Ifixit has a teardown of the device, and there is a big test point labeled "USB BOOT" on the main board, and two smaller ones labeled "RX" and "TX"....
http://guide-images.ifixit.net/igi/UapMeZFPXthjTrEn.huge
Click to expand...
Click to collapse
One way to make the device harder to alter is by making these test points the physical connections for a bootloader USB port. Perhaps the USB port accessible to the user is solely intended as a data transfer port for multimedia where the driver is initialised only after the anti-hacking measures are loaded?
pokey9000 said:
USB boot needs a special boot loader (aboot in omap4boot used in Firekit) , and at least on the Nook Tablet it needs to be signed too. I doubt that TI's customers can or would opt for locking just flash boot so I'm going to assume that it won't work on the new Fires without a signed USB loader.
Click to expand...
Click to collapse
This is standard operating practice. You can be assured that if flash boot is locked, USB boot will also be locked.
Interesting tidbit: While no Samsung Android device other than the Verizon GS3 (and rumor has it, upcoming Verizone Note 2) has a locked bootloader in terms of ability to boot a kernel, nearly ALL of them have the initial first stage of boot locked. It's just that Samsung usually drops the chain of trust early on. This is, for example, why Unbrickable Mod doesn't exist for any GS2 or GS3-family device - No one has access to a signed USB-bootable IBL/PBL/SBL setup. (Technically, one could likely USB-boot the existing IBL, but that IBL is hardcoded to go to flash for PBL/SBL.)
So far, no one I am aware of has ever compromised the low-level hardware enforcement of OMAP4 HS or Exynos4. In all cases of OMAP4, any compromise took advantage of holes in the chain of trust farther down the line - however nearly all attack vectors are known, so probably every compromise technique that is standard (kexec, second init, etc.) has a countermeasure in play with the KFHD if they're THAT confident in its unbreakability. In the case of Exynos4, in all current cases the chain of trust goes "insecure" so early that only people with clobbered bootloaders care.
If you send me kfhd Roms I will test.there's only one,I know of that horrible cm10 Rom
I was wrong about the cm10 ROM ts beast.just gotta wait for cm10.1
Sent from my KFTT using xda premium
Kindle Fire ROM Test
KindleFireGuy said:
If you send me kfhd I will test.there's only one,I know of that horrible cm10 Rom
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
KindleFireGuy,
Thank you for the offer, we may take you up on this when we launch Ubuntu for the Kindle Fire HD and 2.
WOW thanks I will gladly test thanks
Sent from my KFTT using xda premium
Custom ROM for The Kindle Fire HD 7" and 2 - Ubuntu Linux
KindleFireGuy said:
WOW thanks I will gladly test thanks
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
KindleFireGuy,
We are a few weeks or two away, plenty of bugs to iron out before we are even Beta Ready.
I assume you mean a release for the kfhd 8.9?
Sent from my GT-P3110 using xda app-developers app
prokennexusa said:
KindleFireGuy,
We are a few weeks or two away, plenty of bugs to iron out before we are even Beta Ready. I am very shocked that developers released the CM10 ROM, I feel it is way too Green to have anyone waste there time on the installation. We would never release anything to the public that can not even display the boot screen well, it gives CM10 a bad name - just my opinion.
We will let you know when we are ready - we are not trying to be the first, we are trying to have the best ROM available. If it is not as stable or MORE stable than the Kindle original ROM we will not release it to the public.
Click to expand...
Click to collapse
I'm a bit surprised by your opinion honestly. The cm10 for the KFTT only has two bugs. One is pretty minor (the boot screen. Yes, I would prefer it to be correct but... more to follow). The second bug is lack of HD.. that one I see as a major bug. But for me my choices are- 1. Run the Amazon Rom and HOPE the notifications work in a timely manner BUT I can run Netflix. Or 2- run a Rom that allows me to get notifications on time (for me MUCH more important. I'm very surprised that the stock Amazon OS handles notifications so poorly since even my Windows 8 box does that right lol
Now, the cm10 roms for the other devices are barely functional so I would understand, but what Hashcode has accomplished here is pretty darn good. ESPECIALLY having TWRP..
I DO really look forward to trying the ubuntu Rom though..
Edit: as for the initial post here.. dude is asking about kfhd roms but is posting from his kf2? I THINK the cm10 build he is talking about is for the kfhd 7" NOT the kf2 rom
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Removed
Messed up on it.don't send me a hd I already have one I messed up on typing
Sent from my KFTT using xda premium
The Kindle Fire 2
I have a kindle fire 2 and am surprised that people cannot hack the bootloader on it yet. I say this because I have had all the Apple Ipad and Iphone and everyone has been able to hack them with no problem, although it took them awhile!
So I hope that someone is able to get the bootloader unlocked for the Kindle Fire 2, HD to enable the installation of custom roms. Personally I just want to take an image of the KF2 and put it on my KF1 (both uk versions!).
Canonical Ubuntu Linux for Android
mindmajick said:
I'm a bit surprised by your opinion honestly. The cm10 for the KFTT only has two bugs. One is pretty minor (the boot screen. Yes, I would prefer it to be correct but... more to follow). The second bug is lack of HD.. that one I see as a major bug. But for me my choices are- 1. Run the Amazon Rom and HOPE the notifications work in a timely manner BUT I can run Netflix. Or 2- run a Rom that allows me to get notifications on time (for me MUCH more important. I'm very surprised that the stock Amazon OS handles notifications so poorly since even my Windows 8 box does that right lol
Now, the cm10 roms for the other devices are barely functional so I would understand, but what Hashcode has accomplished here is pretty darn good. ESPECIALLY having TWRP..
I DO really look forward to trying the ubuntu Rom though..
Edit: as for the initial post here.. dude is asking about kfhd roms but is posting from his kf2? I THINK the cm10 build he is talking about is for the kfhd 7" NOT the kf2 rom
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Click to expand...
Click to collapse
mindmajick,
I think we are on two totally different pages. I am very well aware of Hashcodes work on the Kindle Fire 2 which is down right impressive. I have tested there work on the Kindle Fire 2 for the last week (almost 10 days now) and all we found was two minor issues and one major issue.
What I am talking about and I will be clear this time (sorry I was not clear in the post) is the Kindle Fire HD 7", the one that was released about 7 months ago and has software revisions of 7.2.x - we did test 1 version as well as compiling our own AOSP, CM10 and AOKP. The latter was a complete failure but it was not due to the Kernel's fault, it was due to the know issues around compiling Kernels around the Kindle Fire HD 7" plus there are limited resources available on the Kindle HD 7" and Custom ROM's.
Anyways, the Kindle Fire HD 7" and 8.9" are exciting platforms to builds around, we have been on the phone and emailing TI almost daily (working to get the proper drivers built into the Kernel's). Thank God we have the support of Ubuntu, otherwise this path would be even more difficult.
The idea around Ubuntu is very different than CM10 and the rest. The idea with Ubuntu is to completely replace the desktop computer, so by day, your phone go with you and at night you dock the phone. The phone via the dock, is connected to an external Printer, Monitor, Keyboard and Mouse. The Ubuntu Phone becomes your home PC. No need for separate ISP, no need for another PC, no need to sync you work. The big question, what about the Google Play Store Apps, no problem. Ubuntu supports Android Apps natively as well as supports the entire array of Ubuntu apps already available (most are free). Release timeline? Hard to say, if it was our choise we would release a copy for the Kindle today but we are under tight constrains with Canonical. They tell us when it is OK to release the software.
More to come........................
prokennexusa said:
mindmajick,
I think we are on two totally different pages. I am very well aware of Hashcodes work on the Kindle Fire 2 which is down right impressive. I have tested there work on the Kindle Fire 2 for the last week (almost 10 days now) and all we found was two minor issues and one major issue.
What I am talking about and I will be clear this time (sorry I was not clear in the post) is the Kindle Fire HD 7", the one that was released about 7 months ago and has software revisions of 7.2.x - we did test 1 version as well as compiling our own AOSP, CM10 and AOKP. The latter was a complete failure but it was not due to the Kernel's fault, it was due to the know issues around compiling Kernels around the Kindle Fire HD 7" plus there are limited resources available on the Kindle HD 7" and Custom ROM's.
Anyways, the Kindle Fire HD 7" and 8.9" are exciting platforms to builds around, we have been on the phone and emailing TI almost daily (working to get the proper drivers built into the Kernel's). Thank God we have the support of Ubuntu, otherwise this path would be even more difficult.
The idea around Ubuntu is very different than CM10 and the rest. The idea with Ubuntu is to completely replace the desktop computer, so by day, your phone go with you and at night you dock the phone. The phone via the dock, is connected to an external Printer, Monitor, Keyboard and Mouse. The Ubuntu Phone becomes your home PC. No need for separate ISP, no need for another PC, no need to sync you work. The big question, what about the Google Play Store Apps, no problem. Ubuntu supports Android Apps natively as well as supports the entire array of Ubuntu apps already available (most are free). Release timeline? Hard to say, if it was our choise we would release a copy for the Kindle today but we are under tight constrains with Canonical. They tell us when it is OK to release the software.
More to come........................
Click to expand...
Click to collapse
Yup. I guess I misunderstood.
I hope to see Ubuntu on the kf2 as well
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Fo
mindmajick said:
Yup. I guess I misunderstood.
I hope to see Ubuntu on the kf2 as well
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Click to expand...
Click to collapse
mindmajick,
No worries mindmajick, this happens, I catch myself doing it from time to time. Yes, we will have Ubuntu for all Kindles. Again, timeline is a bit unknown even though we could post a viable ROM for the Kindle Fire 2. we will post updates as progress is made on this topic. Have a great week!
prokennexusa said:
mindmajick,
No worries mindmajick, this happens, I catch myself doing it from time to time. Yes, we will have Ubuntu for all Kindles. Again, timeline is a bit unknown even though we could post a viable ROM for the Kindle Fire 2. we will post updates as progress is made on this topic. Have a great week!
Click to expand...
Click to collapse
why dont post an alpha ubuntu version?
persano said:
why dont post an alpha ubuntu version?
Click to expand...
Click to collapse
persano,
The Ubuntu ROM for Android is Stable on our Kindle, we could launch a production copy today, the problem is the contract that we sign with Ubuntu Canonical. This contract does not allow us to release any copies of Ubuntu for Android until Canonical is ready to launch Ubuntu for Android.
So we are just staying busy writing new Apps for Ubuntu rather than focus our efforts on rushing the Production version. Do not get me wrong, we spend plenty of time each week on the ROM, streamlining it and making it faster.
It would not be a good idea to release the ROM today anyway since this ROM is intended to replace the desktop computer. Having said this, we are missing a Key part - a dock for the Kindle to add an external Monitor, Keyboard, Mouse, and Printer. When the manufactures begin to release docks, we will release the ROM. Do not worry, if Amazon does not release a dock, we will still release the ROM, it may be a few months or two away, that is all.
prokennexusa said:
persano,
The Ubuntu ROM for Android is Stable on our Kindle, we could launch a production copy today, the problem is the contract that we sign with Ubuntu Canonical. This contract does not allow us to release any copies of Ubuntu for Android until Canonical is ready to launch Ubuntu for Android.
So we are just staying busy writing new Apps for Ubuntu rather than focus our efforts on rushing the Production version. Do not get me wrong, we spend plenty of time each week on the ROM, streamlining it and making it faster.
It would not be a good idea to release the ROM today anyway since this ROM is intended to replace the desktop computer. Having said this, we are missing a Key part - a dock for the Kindle to add an external Monitor, Keyboard, Mouse, and Printer. When the manufactures begin to release docks, we will release the ROM. Do not worry, if Amazon does not release a dock, we will still release the ROM, it may be a few months or two away, that is all.
Click to expand...
Click to collapse
i understand
Ubuntu for Android on Kindle Fire HD
persano said:
i understand
Click to expand...
Click to collapse
persano,
Once they allow us to release copies to employees I will get you a copy to test.
prokennexusa said:
persano,
Once they allow us to release copies to employees I will get you a copy to test.
Click to expand...
Click to collapse
Really look forward to seeing this, Keep me in mind if you decide to leak a few copies for testing I would be more then happy to help out. Always loved Ubuntu on the desktop/
prokennexusa said:
KindleFireGuy,
We are a few weeks or two away, plenty of bugs to iron out before we are even Beta Ready. I am very shocked that developers released the CM10 ROM, I feel it is way too Green to have anyone waste there time on the installation. We would never release anything to the public that can not even display the boot screen well, it gives CM10 a bad name - just my opinion.
We will let you know when we are ready - we are not trying to be the first, we are trying to have the best ROM available. If it is not as stable or MORE stable than the Kindle original ROM we will not release it to the public.
Click to expand...
Click to collapse
This is kind of a poor attempt at a troll don't you think?
1. No where in ReverendKJr's thread does he claim to be an expert coder who is releasing a fully usable ROM. Everything is very clear in the OP that he is showcasing some of the work VeryGreen did on the KFHD8.9 and trying "learn as he goes" and port some of that over to the KFHD7.
You: A dev who hasn't posted anything in the "dev" section yet, trying to belittle someone who has; is like a 5 year old scribbling over their neighbor's painting so that everyone will look at theirs instead.
2. Not many users are looking for an Ubuntu Desktop ROM on their KFHD. I can safely speak for the majority of this community: they're waiting for AOSP Android in some fully functional form. Tho, if you are hinting that you have a working copy of unreleased Ubuntu Phone, I'm sure there will be some interest in that as well.
3. You mention being on the phone with TI daily. But let me ask you ... why? There are publicly available resources to gather almost any information you need on TI products. And about the ONLY thing that's really made by Texas Instruments in the Kindle Fire HD's is the CPU and the battery gauge. Everything else about the device is some other manufacturer. And to prove it here's a QUICK breakdown of the KFHD8.9 of which the 7" is very similar:
*CPU: TI OMAP4470 @ 1.5Ghz
InvenSense MPU6050 w/ Gyroscope, Accelerometer and Compass (Aichi Steel ami306)
Light Sensor: Maxim MAX44007
*Battery Gauge: TI BQ27541
Charger: Summit SMB347
Wifi: Broadcom 4330 wlan
Audio: Wolfson Micro’s WM8962E
Touchscreen: Cypress TrueTouch
LCD: NT71391 Hydis 1920x1200 WUGA DSI
Here are random sources off the top of my head which would serve you better than a phone call to a now very understaffed mobile/smart phone department:
http://www.omapzoom.com
http://dev.omapzoom.com
http://www.omappedia.org/wiki/Main_Page
https://gforge.ti.com/gf/
4. I'm curious how you plan on solving the M3/ducati issues presented by running in Ubuntu. This would be the 2x sub processors normally designed to run HD codecs and camera. In Android, they are coded with a real time OS which communicates with the OMX integration layer (see: hardware/ti/omap4xxx/domx in Android source for more info). In Ubuntu, they don't use OMX, instead opting for g-streamer and other solutions. The ducati presented by Amazon uses OMX. Not G-Streamer. So unless you're planning on software decoders (less than desirable), this is going to be an issue.
So I'm going to call your bluff: Show me yours and I'll show you mine. Feel free to PM me.
Mine:
I have CM10.1 booting on the KFHD8.9. I'm re-writing the userspace audio driver from scratch (not done) and the HD codecs/camera functions need tweaks. Working Display, Wifi, BT, Sensors, etc. It's running a 3.0.50 kernel based on TI's latest OMAP4 kernel release. It's fully enhanced with blitsville drivers and brand new PowerVR graphics drivers released only a few days ago.
Sources:
https://github.com/KFire-Android/android_local_manifest
Specically, kernel: https://github.com/KFire-Android/kernel_omap_bowser-common
(You may note that I've left a place holder device for the KFHD7 which is pre-set up with as much information as I have currently.)
I have publicly admitted that I'm overbooked with devices and wasn't planning on supporting the KFHD7.. BUT that doesn't stop another dev from looking at my work on the KFHD8.9 and porting it to the KFHD7.
In closing:
1. Don't insult devs who are looking to help out in a community that is lacking. Everyone needs to start somewhere and who knows what may come of it.
2. Development isn't "dead" on the KFHD7. It's just in a deep state of slumber.
Hashcode said:
This is kind of a poor attempt at a troll don't you think?
1. No where in ReverendKJr's thread does he claim to be an expert coder who is releasing a fully usable ROM. Everything is very clear in the OP that he is showcasing some of the work VeryGreen did on the KFHD8.9 and trying "learn as he goes" and port some of that over to the KFHD7.
You: A dev who hasn't posted anything in the "dev" section yet, trying to belittle someone who has; is like a 5 year old scribbling over their neighbor's painting so that everyone will look at theirs instead.
2. Not many users are looking for an Ubuntu Desktop ROM on their KFHD. I can safely speak for the majority of this community: they're waiting for AOSP Android in some fully functional form. Tho, if you are hinting that you have a working copy of unreleased Ubuntu Phone, I'm sure there will be some interest in that as well.
3. You mention being on the phone with TI daily. But let me ask you ... why? There are publicly available resources to gather almost any information you need on TI products. And about the ONLY thing that's really made by Texas Instruments in the Kindle Fire HD's is the CPU and the battery gauge. Everything else about the device is some other manufacturer. And to prove it here's a QUICK breakdown of the KFHD8.9 of which the 7" is very similar:
*CPU: TI OMAP4470 @ 1.5Ghz
InvenSense MPU6050 w/ Gyroscope, Accelerometer and Compass (Aichi Steel ami306)
Light Sensor: Maxim MAX44007
*Battery Gauge: TI BQ27541
Charger: Summit SMB347
Wifi: Broadcom 4330 wlan
Audio: Wolfson Micro’s WM8962E
Touchscreen: Cypress TrueTouch
LCD: NT71391 Hydis 1920x1200 WUGA DSI
Here are random sources off the top of my head which would serve you better than a phone call to a now very understaffed mobile/smart phone department:
http://www.omapzoom.com
http://dev.omapzoom.com
http://www.omappedia.org/wiki/Main_Page
https://gforge.ti.com/gf/
4. I'm curious how you plan on solving the M3/ducati issues presented by running in Ubuntu. This would be the 2x sub processors normally designed to run HD codecs and camera. In Android, they are coded with a real time OS which communicates with the OMX integration layer (see: hardware/ti/omap4xxx/domx in Android source for more info). In Ubuntu, they don't use OMX, instead opting for g-streamer and other solutions. The ducati presented by Amazon uses OMX. Not G-Streamer. So unless you're planning on software decoders (less than desirable), this is going to be an issue.
So I'm going to call your bluff: Show me yours and I'll show you mine. Feel free to PM me.
Mine:
I have CM10.1 booting on the KFHD8.9. I'm re-writing the userspace audio driver from scratch (not done) and the HD codecs/camera functions need tweaks. Working Display, Wifi, BT, Sensors, etc. It's running a 3.0.50 kernel based on TI's latest OMAP4 kernel release. It's fully enhanced with blitsville drivers and brand new PowerVR graphics drivers released only a few days ago.
Sources:
https://github.com/KFire-Android/android_local_manifest
Specically, kernel: https://github.com/KFire-Android/kernel_omap_bowser-common
(You may note that I've left a place holder device for the KFHD7 which is pre-set up with as much information as I have currently.)
I have publicly admitted that I'm overbooked with devices and wasn't planning on supporting the KFHD7.. BUT that doesn't stop another dev from looking at my work on the KFHD8.9 and porting it to the KFHD7.
In closing:
1. Don't insult devs who are looking to help out in a community that is lacking. Everyone needs to start somewhere and who knows what may come of it.
2. Development isn't "dead" on the KFHD7. It's just in a deep state of slumber.
Click to expand...
Click to collapse
please, tell us what you did so we can do it in the kindle fire 7"
and yeah, i want android, not ubuntu, ubuntu is beautiful, but i tweak for android, i love android!
give me a clean 8.9 build.prop from amazon, so i can add this device to my tweaks
Hashcode,
We have been in business since 1982 and have nothing to prove to anyone, certainly not you - our business speaks for itself. I respect you work and although I do not agree with all your decisions I still respect you as a developer and believe you are quite a genius - we have spoken in such a fashion in quite a few posts.
This is the beauty of this community, we can all have different ideas, different platforms and different OS's - all meet together as developers to share and be part of an overall goal to improve the end users experience. We never said ours was the best. We can have an open dialogue and not always agree but in the end we can respect on another.
This is a ridiculous response and I will not respond or waste any more time on it other than this one response.
We may not even be allowed to post the ROM in the end since Canonical Ubuntu has not made a final decision on it's marketing strategy. In the end, we may only be allowed to post apps for Canonical, everything is in the air at the moment. This just fine with us since we resell there other products and the Kindle Development is about 1% of our total monthly business.
We specialize in Anti-Spam, have you heard of Postini? We developed an anti-spam engine back in 2002 that was eventually bought by Postini, which was eventually sold to Google. Anyway, this too is a small part of my total company revenue. So I have done my share of development work - this is just a hobby to us, not a primary means of income. As a matter of fact, we decline to charge most customers that send there Kindle back to us for data recovery. This is one of the many gifts we offer to people in the XDA Community.
Rather than get upset, why don't YOU apply to be a developer for Canonical and bring on competition within the Ubuntu world? We would love to have you aboard, if you meet the minimum business requirements.
Just like yourself, we are here to share our abilities with the XDA Community. One thing we refuse to do is dialogue with someone who has posted an aggressive response like you have done. We have done nothing but spoken highly of your work, we have mentioned your name in several posts so we really do not deserve this kind of garbage.
This would have been far better received in a Private message or call to our number which is posted in every response. I am sure we pressed buttons with you or have somehow become a threat which I really do not understand? There is plenty of room for everyone here in XDA and I love competition - this is how I came up with my name, I am sponsored by Prokennex - Michael Martinez is a good friend of mine.
Let's just see what happens over the next few months, I believe of letting action speak, not words. This site is NOT our primary means of income, we own a large data center and manage over 650 customers - we are an IT Company that manages companies like: Kaiser Permanente in Oakland, Chevron Corp in Dublin CA, Wells Fargo Bank in Oakland, Alcan Plastic Packaging in Newark, VTA Transit in Santa Clara and many more.
Between my company and Racquet Ball, I have absolutely no free time!
We are honored to be a part of the XDA Community allowing us to share our expertise and experience, this is our goal here in XDA Developers, not to impress you or anyone else.
Finally, we joined Ubuntu quite a few years ago reselling there desktop and server platform as a Windows replacement. When they discussed releasing the Ubuntu for Phones and Ubuntu for Android, the idea fit our vertical market perfectly so we joined this solution at the 2013 CES show. The idea is to replace the desktop workstation, which will happen since phones & tablets have plenty of power to perform such a task - I am just surprised it took this long to come to reality.
God Bless.
I would like to jailbreak this Fire and be able to add apps and use it as a dedicated device for a specific purpose. When I attempt to download the apps from the Amazon app page I see a notice that the device is not supported. I know I purchased this device in 2012 or 2013, so I know it is old.
So tell me would it be possible to jailbreak this device and put current Android OS on it and download some specific apps?
kybunnies said:
I would like to jailbreak this Fire and be able to add apps and use it as a dedicated device for a specific purpose. When I attempt to download the apps from the Amazon app page I see a notice that the device is not supported. I know I purchased this device in 2012 or 2013, so I know it is old.
So tell me would it be possible to jailbreak this device and put current Android OS on it and download some specific apps?
Click to expand...
Click to collapse
Do you have a HD 8.9 or HDX 8.9? They are very different devices with different paths to FireOS freedom.
Davey126 said:
Do you have a HD 8.9 or HDX 8.9? They are very different devices with different paths to FireOS freedom.
Click to expand...
Click to collapse
I have the Kindle Fire HD 8.9. If I posted in the wrong thread I apologize.
kybunnies said:
I have the Kindle Fire HD 8.9. If I posted in the wrong thread I apologize.
Click to expand...
Click to collapse
No worries. You have a 2nd generation Fire HD 8.9 code named "jem". I have the 7 inch mode code named "tate". Both can be unlocked and accommodate a variety of custom ROMs. However, the path is not easy and will take a significant investment on your part to read up on techniques an caveats and then successfully apply them to your device. The following threads should prove helpful:
https://forum.xda-developers.com/kindle-fire-hd/8-9-inch-help
https://forum.xda-developers.com/kindle-fire-hd/8-9-development
Alternatively, you can purchase a package that will simplify the process. This is one example:
https://www.perfectlyandroid.com
The site may look childish but the product is the real deal. That said, it is likely the support staff has moved on as 2nd generation devices haven't been sold since 2012. You may not need them but you'd probably want to confirm availability before laying down any coin.
Keep in mind this device is 6+ years old with limited capabilities even with a custom ROM. A $40 phone from WalMart will easily run circles around this pup.
Good luck.
So it would probably be better to purchase a new/newer device for what I want. I mainly want the device to use as a dedicated bible with bible apps. I have a new Kindle Fire 7 inch with a 64 GB micro SD card. But with having 20-50 books , Calibre Companion, Moon+Reader pro and one bible app takes up all memory. This is before adding any additional purchases from the bible app. I have it where apps are suppose to be stored on the SD card but that does not help. I honestly hate getting rid of this Kindle Fire 8.9 since it is still working and holds a charge. I admit that I have side loaded most of the apps I want but I can't get one app to login so my info/notes will sync. This is why I thought about jailbreaking the device to see if I could get a new version of the app installed. Maybe I wold be better off searching for a refurbished iPad or buying a new Kindle Fire 8 or 10 inch. Something to think about.
Thanks so much for the help.
kybunnies said:
So it would probably be better to purchase a new/newer device for what I want. I mainly want the device to use as a dedicated bible with bible apps. I have a new Kindle Fire 7 inch with a 64 GB micro SD card. But with having 20-50 books , Calibre Companion, Moon+Reader pro and one bible app takes up all memory. This is before adding any additional purchases from the bible app. I have it where apps are suppose to be stored on the SD card but that does not help. I honestly hate getting rid of this Kindle Fire 8.9 since it is still working and holds a charge. I admit that I have side loaded most of the apps I want but I can't get one app to login so my info/notes will sync. This is why I thought about jailbreaking the device to see if I could get a new version of the app installed. Maybe I wold be better off searching for a refurbished iPad or buying a new Kindle Fire 8 or 10 inch. Something to think about.
Thanks so much for the help.
Click to expand...
Click to collapse
Installing a different Android version on any of the Amazon Fire's requires a custom rom.
Installing a custom rom requires either a unlocked bootloader or root access.
None of the 5th gen or newer have any means of unlocking the bootloader, and only the 7th gen HD 10 has a root method, but no custom roms.
Sent from my PH-1 using Tapatalk
sd_shadow said:
Installing a different Android version on any of the Amazon Fire's requires a custom rom.
Installing a custom rom requires either a unlocked bootloader or root access.
None of the 5th gen or newer have any means of unlocking the bootloader, and only the 7th gen HD 10 has a root method, but no custom roms.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Please do not take my response as being smart/snarky. I honestly do not understand a word you said except I can't jailbreak any Kindle Fire that is 5th generation or newer.
Only reason I want to jail break this one is because I cannot install a couple of apps that I want.
kybunnies said:
Please do not take my response as being smart/snarky. I honestly do not understand a word you said except I can't jailbreak any Kindle Fire that is 5th generation or newer.
Only reason I want to jail break this one is because I cannot install a couple of apps that I want.
Click to expand...
Click to collapse
Jailbreak is an iPhone thing, does not apply to Android or in this case FireOS.
If is to just an apps problem, that doesn't necessarily mean you need to do any modifications like root.
The apps just do not install?
Sent from my sailfish using XDA Labs
sd_shadow said:
Jailbreak is an iPhone thing, does not apply to Android or in this case FireOS.
If is to just an apps problem, that doesn't necessarily mean you need to do any modifications like root.
The apps just do not install?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Okay I am showing how much I do not know about this stuff.
When I go to the app page at Amazon my device is not supported. The app is free so I have downloaded it and tried to sideload it. Again it will not install. I have found older versions of the app and some will install but they will not allow me to login and sync my info. I can login to the apps website via the device without any problems. The Wi-Fi signal is strong so that is not the problem. On my Kindle Fire purchased in July (used for digital books) the apps installs easily and I am able to log in.
Yes I know it would be easier to just put the app on the newer Kindle but the screen is smaller and some of the older adults at church enjoy seeing/reading all the different versions I pull up on the Bible. I just want to put the app on the larger screen Kindle and make it easier for everyone to see.
As stated in the title. When I send a push to my Fire it doesnt appear in the notifications. I need to open the pushbullet app, and then I get the notification, which is really annoying. Any way to fix this?
GreeTech said:
As stated in the title. When I send a push to my Fire it doesnt appear in the notifications. I need to open the pushbullet app, and then I get the notification, which is really annoying. Any way to fix this?
Click to expand...
Click to collapse
Title states "Fire HD 7” but that model was discontinued years ago. Guessing you have a 7th gen Fire 7 which runs a version of FireOS based on Android 5.1.
Unfortunately, Amazon has crippled the notification mechanism in FireOS. Some work; many do not. You will need to root/unlock and install a custom ROM to restore full functionality. From a time/effort perspective it would be more efficient to purchase a different tablet that runs vanilla Android out of the box. Walmart sells a few varients; the $64 (US) ONN 8" is an attractive alternative.
Davey126 said:
Title states "Fire HD 7” but that model was discontinued years ago. Guessing you have a 7th gen Fire 7 which runs a version of FireOS based on Android 5.1.
Unfortunately, Amazon has crippled the notification mechanism in FireOS. Some work; many do not. You will need to root/unlock and install a custom ROM to restore full functionality. From a time/effort perspective it would be more efficient to purchase a different tablet that runs vanilla Android out of the box. Walmart sells a few varients; the $64 (US) ONN 8" is an attractive alternative.
Click to expand...
Click to collapse
Just checked, sorry. I meant Android 7, so it's the Fire HD 8 :/
GreeTech said:
Just checked, sorry. I meant Android 7, so it's the Fire HD 8 :/
Click to expand...
Click to collapse
No, it can be the newest fire 7 2019. What is the device name?
Rortiz2 said:
No, it can be the newest fire 7 2019. What is the device name?
Click to expand...
Click to collapse
Fire HD 8, 8. Generation
Rortiz2 said:
No, it can be the newest fire 7 2019. What is the device name?
Click to expand...
Click to collapse
Fire 7 2019 - Mustang
---------- Post added at 03:34 AM ---------- Previous post was at 03:21 AM ----------
Do you have to modify the framework-res.apk (Android System) on your rooted Fire 7 2019 to work the pushes and appear the notifications on Pushbullet
Can you find the files on decompiled framework-res.apk
Code:
/res/values/bools.xml
Find the code, replace false with true
Code:
<bool name="config_smsCapable">true</bool>
<bool name="config_voiceCapable>true</bool>