Project OtterX: New Direction - Kindle Fire General

** WARNING. WORK-IN-PROCESS DISCUSSION. NO ETAS. NO DONATIONS. NO PROMISES. **
PROJECT OTTER X DISCUSSION
It's a major change to the device. If you choose to update, it won't be easy to flash back the stock files and use your device as a Kindle again. The device name will actually change to "otterx", so that the 2 sets of files can be kept clearly distinct as well as provide a safety net for those who accidentally download the wrong thing and try to flash it.
GOALS OF THIS PROJECT: Make everyone happy of course.
[DONE] Update the bootloader (u-boot). And I don't mean "tweaks" to the bootloader, I mean: the current code was based on a 2011 release. The newer bootloader will be based on a 2014 release. Changes to be included in the update:
[DONE] A much better text driven menu system laid on-top of the initial boot graphic (as opposed to the image-only menus currently)
[DONE] Cleaned up device initialization / charging loop for extreme low battery situations
[DONE] Support devtree binary loading (native support for newer kernels)
[DONE] Support for decompessing kernels in new formats
[DONE] Native "reboot recovery" support no more hacky idme/sticky values
[DONE] Device "handling" changes like a longer button press to fully power on the device. Avoids "accidental" power ons while traveling.
[DONE--NEED NEW OTTERX ROM] Built in support for "charger" mode. IE: plug the device in while it's off and it boots into the native Android charger screen, vs a full boot of Android.
[DONE] I'm guessing a new initial power-on logo as well (it says "KINDLE" -- I lied.. but you can change it!)
[DONE] Partition layout change to support 5 to 6gb of combined app / sdcard storage.
[DONE] Rebuild a new TWRP to support combined data/storage
[DONE] The process for changing the partition layout is be handled in the bootloader menu. Users will need to pull everything off the internal storage prior to performing the change as it will wipe system, cache and userdata partitions out during the process.
[DONE] Kernel and userspace now support F2FS format for userdata. This is a new filesystem specifically designed for devices which use EMMC style storage.
Kernel update. A lot has happened to the OMAP kernel world over the last year. Much of the code needed to run newer kernels has been merged into the mainline. However, much has not. So I'm riding the line between: 1) finishing the 3.4 kernel using the new bootloader and partition layout, with an option for upgrading later to an even newer one. Drawback: I don't have a 512MB based ducati binary to process HD codecs for the 3.4 kernel. Or, 2) starting a newer kernel to go hand in hand with the other portions of this update (it would be 3.8 or newer). Why upgrade the kernel? Besides the typical "bigger better faster" mentality, I want some specific solutions to current problems: our graphics layer has been outdated for 1-2 versions of Android, and we still use a TI supplied ducati binary for HD codecs. If we update to a 3.8+ kernel, I can then attempt to build a custom ducati binary which would work better with our 512MB memory requirements and leave more free space to the OS.
Of course, the REAL end goal: to keep this device current and usable using today and future OS updates. And yes, maybe even get OTG and the MIC functions working.

reserved

yes i would update immediately
edit
Multi boot isn't a priority for me and as you say space is key with the kindle.
the new partitions sounds great.
Sent from my Nexus 5 using Tapatalk

My kindle is my toy. I burn any rom I can on it, and make backups to store off kindle. I have other equipment, would probably try to make an image before changing. But I would play with it!
I do not want to dual boot. I use virtual environments on my desktop for other os.
Sent from my Nexus 7 using xda app-developers app

1) I would absolutely perform this update. No - I never had an intention to use this device as a stock Kindle Fire Reader.
2) I really can't say if it would appeal to others. But the rationale makes sense to me.
3) I agree - better to have one VERY usable ROM.

This project is exactly what this device needs.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks for your ideas. These ideas will make KF an interesting device to develop and test apps.
Sent from my Amazon Kindle Fire using Tapatalk

1 - I would definitely repartition etc.
2 - I think most current users would also
3 - I wouldn't personally dualboot
I would also love Ubuntu with a similar partition layout,
Thanks for the continuous support, it has provided a great user experience

I wouldn't mind not going back to kindle software.

1. Would you perform such an update knowing that you would have a hard time going back to the Amazon software.
Yes, definitely
2. If I were to drop the partition layout change from this project do you think more users would like it? Or less?
Less
3. I had considered a dual boot option to be built into the new menu system.
Drop the dual-boot idea
Kevin

Yes for all 3, it will make the kindle much more better and faster
Sent from my Moto G using xda app-developers app

just ordered a replacement screen for my emmc damaged kindle, so i will also be trying your unbrick procedure soon. thanks so much for all your work Hash. its greatly appreciated. cheers Steve
Sent from my Nexus 5 using Tapatalk

Hashcode, it would be great to see you take Kindle Fire development in this direction. The plans are grand and it's obviously going to take a lot of work, but it would certainly breathe new life into the device. If you're going to do it, I say you swing for the fences. My guess is most people around this forum are here for the full android experience and not so worried about leaving the amazon ecosystem behind. Plus, the storage capacity on the KF has been a sore point from the beginning, so combining the userdata and sdcard partitions is really the best way to optimize usage for all users. With those two things in mind, I think it's a relatively easy decision to repartition as you've planned and forgo dualboot (which will also complicate the emulated sdcard usage anyway). Eagerly looking forward to the great things to come! :good::good:

Hashcode said:
DISCUSSION POINTS:
1. Would you perform such an update knowing that you would have a hard time going back to the Amazon software. Who really uses their original Kindle Fire as a reader anymore anyway?
2. If I were to drop the partition layout change from this project do you think more users would like it? Or less?
3. I had considered a dual boot option to be built into the new menu system. But I think we just don't have the internal space for it. I'd rather have 1 VERY usable tablet, than a dual boot system which isn't as usable in either ROM. Thoughts?
Click to expand...
Click to collapse
I really love your idea for otterx.
On your discussion points:
1. Yes, I would update for sure
2. The partition layout change seems like it is key to otterx. If the partitioning is manual it will cause problems for some. If it is automatic then everyone will love it. Neither of these options will scare me away BTW.
3. I prefer a single ROM that is stable/usable versus two unstable dual boot ROMs.
Even if otterx doesn't get off the ground, thanks again for helping keep this HW relevant.

1. I would update for sure.
2. The partition idea seems brilliant since space is a key constraint. It would also be great to have OTG working.
3. No need for dual boot.

My vote
I just want to cast my vote for Project OtterX along with everyone else. I'd update (I haven't run Amazon software in my KF for more than two years). The partitioning is key and necessary to keep the KF usable with future OS updates. As with others, dual boot isn't important to me.

1) I would totally update, been years since my last boot of the Amazon OS. I can get any Amazon App from Google Play, Non-Amazon Prime Users should NOT have a problem, unless they are and usae Instant Video.
2) In theory this should way better, but there might be a problem: Harder Developing. If it is in fact harder to develop a ROM for this specific type of system, we may look into very few ROMs available, which I am pretty sure I community does NOT want. Even though, I am doubtful it will get any harder.
3) Dual Booting might be awesome, but on this device, the Hardware will be much slower and otherwise defeat the purpose of building this new "OtterX".
In other words, I FULLY AGREE, that we should continue or start the OtterX project. We might wanna do a poll to assure that our community in fact will want this. Hope you have success in this Hashcode!!!
Sent from my Amazon Kindle Fire using xda app-developers app

Dual booting can be really useful for me specially if we can boot tar images easily with chroot with also a specific kernel instead of repartitioning every time

Small update as I work on the new bootloader.
Some of the new screens.
Image #1: I really like the new ultra simple bootscreen of the HDX's so I thought I'd start there... tho I may still change "kindle fire" to something else.
Image #2: Is the low battery charging screen
Image #3: Is a new screen similar to what the KFireHD 8.9" has for anytime you enter fastboot mode.
(Text responses from fastboot are shown on the fastboot screen)
Once I get the menu system up and running, I'll try and put some shots of that up as well.

Hashcode, you are constantly amazing with what you have managed to make work on this device. I love all the ideas of this project, I'm definitely a #2 user from your first question. I primarily use my Kfire as a reader(Amazon Kindle app) and internet browser, with some gaming/email here and there.
Discussion Points:
1) I definitely would, I tried going back to the Amazon software about a year ago and couldn't stand it then, let alone since all the work you've done in the last year to get the newer 4.3 and 4.4 revs available.
2) I feel this is a less likely to use situation. the Kfire has a horrendous partition layout for a normal tablet use, I know why it was, but compared to how fluid it feels on my Gnex(similar in that it has no SDcard slot either) the kfire could definitely see better usage in your proposed setup.
3) I have no large interest in dual boot myself, as you mentioned it had a limited amount of storage on the device, something I've found running into limits quickly just using Multiple profiles in CM let alone adding a whole extra system of data to the tablet. Personally I'd prefer the tablet made as functional/quick as possible without worrying about a second OS. I'll be perfectly content with one Os that runs great rather than 2 that could both stand to run better.

Related

Noob advice: The current state of Kindle fire custom ROMs

Hi,
(I already have experience with rooting and installing custom roms on my HTC desire.)
A colleague of mine will travel to the US in a few days, and we where thinking of having him buy and bring back two Kindle Fires from there.
I have a few questions about the feasibility of this, and would be very grateful for some info, to avoid spending .
The infos in this forum are very extensive, and it is very difficult to keep the overview (especially since things change so rapidly).
1. How well are the custom roms working at the moment? Are they ready to be used in actual work environments, or are they still too experimental for this?
2. I want a very minimalist rom, the vanilla Google experience (my favourite on the HTC was Oxygen ROM). Any recommendations? ICS would be great, but Gingerbread would be okay, too. Most important is stability.
3. When I will try rooting and flashing the devices that will take place in Europe. Could this cause problems? E.g., the Amazon Marketplace is inaccessible from here (blocks non-US IPs). I assume that wont matter, just wanted to make sure.
Thanks for your help in advance!
rhhd
1:
http://forum.xda-developers.com/showthread.php?t=1533001
http://forum.xda-developers.com/showthread.php?t=1556910
2:
http://forum.xda-developers.com/showthread.php?t=1475054
3:
http://forum.xda-developers.com/showthread.php?t=1519456
http://forum.xda-developers.com/showthread.php?t=1547252
http://forum.xda-developers.com/showthread.php?t=1393862
http://forum.xda-developers.com/showthread.php?t=1288862
maybe this one is also interesting for you:
http://forum.xda-developers.com/showthread.php?t=1382360
CM7 is nice. Completely stable. You'd probably like Barebones CM7. I was using Standing on the Shoulders of Giants CM7 ROM and loved it.
But...I really wanted ICS, so I flashed CM9. It's beautiful, and very stable, however due to no hardware acceleration (yet) you won't have flash and some games seem to not work.
With all that said, stick to flashing a CM7 Rom and you'll be happy, IMO.
Thanks for the responses.
ChicagoGOBLUE said:
due to no hardware acceleration (yet) you won't have flash and some games seem to not work.
Click to expand...
Click to collapse
And this also means no hi-res video support, right?
Or do is just need to have the right app for that?
right - allthrough you can do hi res video with software like mx player does
but this will result in low framerates (stuttering depending on the source) and high battery usage
Thanks again!
One more question: I just noticed the Kindle Fire has only one physical button (power). The Nook Color has at least a few more (Power, Home, Vol+, Vol-).
Is that an annoyance in everyday life on the Kindle? On my HTC I am kind of glad about the Home, Back, Menu and Volume buttons...
(We haven't yet made a final decision between Kindle and Nook.)
there are softbuttons for all this functions and i learned to live with it
in the meantime it is a bit strange for me when i take the gtab from my wife with the hardbuttons
no problem at all ...
rhhd said:
Thanks again!
One more question: I just noticed the Kindle Fire has only one physical button (power). The Nook Color has at least a few more (Power, Home, Vol+, Vol-).
Is that an annoyance in everyday life on the Kindle? On my HTC I am kind of glad about the Home, Back, Menu and Volume buttons...
(We haven't yet made a final decision between Kindle and Nook.)
Click to expand...
Click to collapse
Not gonna lie, the lack of physical volume buttons drives me crazy. Livable now that I have CM9, but if using CM7 the 'volume control' app/widget/whatever, is a good option.
The lack of physical buttons on the kindle fire is a lucky break for developers as ICS is built with soft buttons in mind for the major functions of the OS so the one button isn't really a big problem. If google decides to go back to relying on physical buttons in jelly bean then the kindles custom rom future will be up in the air. For now if I were you i'd stick with CM7 until the developers have a chance to perfect the new kernel they're working on that will allow for better graphics among many other improvements.
I bought and registered my Kindle while I was in the states and I haven't had any problems with it here in Europe. I used the stock ROM for a few months and was only able to access the US Amazon, though I'm American so I don't know how that will effect you.
As for the soft buttons, I didn't have any problems with it. I thought the KF's stock ROM organized it pretty well; it was really easy to access the volume and brightness controls. The only thing I didn't like was that the bottom task bar was really big and, although it shrinks when you have full screen on, I was still annoyed by it. CM7 doesn't have that problem, though as someone else mentioned, apps are necessary to comfortably access volume control.
To sumarize, I think it was worth getting. I'm happy with it.

Samsung Galaxy Express I8730 Q&A

It seems there is very little information on this device so far, and it's spread across several threads. Here's what I found so far:
NOTE: This is for the international version I-8730 and AT&T model I-437. Since I have the I-8730 will add my personal experience on this model only.
Rooting
Using Motochopper. Worked fine in my Vodafone branded I-8720 with 4.1.2 --> http://forum.xda-developers.com/showpost.php?p=40770093&postcount=2
Using Unlockroot.com, reported to work with I-437 --> http://forum.xda-developers.com/showthread.php?t=2037692
Original Samsung Firmware
List of european firmwares for I-8730 (only tested I8730XWAMC4 / OXXAMC3 and I8730XXAMB8 / OXAAMB8 so far) --> http://www.tsar3000.com/Joomla/index.php?option=com_content&view=article&id=856:samsung-i8730-galaxy-express-firmwares&catid=55:samsung&Itemid=82
Unlocking
A member reported the S3 method works. Did not work on my phone. --> http://forum.xda-developers.com/showpost.php?p=38971203&postcount=15
CWM
Working CWM reported by user jjchico, see thread for instructions -> http://forum.xda-developers.com/showpost.php?p=46521596&postcount=121
OUDHS Touch CWM-based Recovery for I-437 (Not tested in I-8730) --> OUDHS Touch CWM-based Recovery
Initial work, no reports yet that it works --> http://forum.xda-developers.com/showthread.php?t=2285898
Custom ROMS
Nothing yet...
Open Source Code (Thanks to tanrsquare)
The following files are available for GT-I8730:
GT-I8730_JB_Opensource.zip
GT-I8730T_JB_Opensource.zip
GT-I8730_HK_JB_Opensource.zip
GT-I8730_LATIN_JB_Opensource.zip
GT-I8730_SEA_JB_Opensource.zip
The following files are available for GT-I437:
SGH-I437Z_ATT_JB_Opensource.zip
SGH-I437_ATT_ICS_Opensource.zip
Other info
Biggest thread yet on I-8730 and I-437 where I got most of the information -->http://forum.xda-developers.com/showthread.php?t=2037692
If you have any other info just post a reply or send PM and I'll update this list.
Jus Some Developments Info
Hey, source codes is available... Just for a heads up for interested devs!
I had browse the web and found that the source codes for i8730 for various models of i8730. These are all available on Samsung open code release center (OSRC) at opensourcesamsung(dot)com. They are as follows:
Classification Model Version Source Code
Mobile Phone GT-I8730 GT-I8730_JB_Opensource.zip
Mobile Phone GT-I8730T AMD2 GT-I8730T_JB_Opensource.zip
Mobile Phone GT-I8730_HK GT-I8730_HK_JB_Opensource.zip
Mobile Phone GT-I8730_LA GT-I8730_LATIN_JB_Opensource.zip
Mobile Phone GT-I8730_SEA GT-I8730_SEA_JB_Opensource.zip
Me am not developer but a user and owner of this model! As a user, there are just much restrictions from stock OS such as carriers limitations, limited features, and all official roms available are according to respective countries carrier and lack of lots of great tweaks and apps. Although root is available, but its limited as few tweaks that I can play with like V6 Supercharger, link2sd etc. That's why I'm always looking forward to customs! They are great! I know that why me nv grab hold of one that can be customized is due to of course simple, cost restriction. This is jus a great, budgeted, with potential (underclocked), fast, 4G device available in market.
To keep things short pls devs just look alittle in this device, and if customized eg, roms, kernels , I believe that other models with the same chipset and GPU can benefit as well! Models like the new Mega 6.3 and also unreleased S4 Mini! They are all using the same Qualcomm MSM8930 Snapdragon 400!!!
Yeah! Go mid-range devices!!! :fingers-crossed:
Thanks tanrsquare, will add that info to the inicial post.
What about CWM?
I suppose you know that without a working (backup, restore) custom recovery, flashing any rom may permanently brick our phone, so, the next step after root shod be CWM Recovery.
Any news about a working one? Saw that the i-437 has one already...
Info about CWM for i8730
Hey, doarmga... I'm quite agree with u. A CWM is quite an essential for customizing ROMs, without it, ODIN will be needed if there are going to be problems, and that's bad as it increases the binary counter... omg.
Me too, am one of the guys looking ard for i8730 recovery which is stable and usable, but I can predict tht none exists yet currently. I have search the web as well as XDA and I came to this site: builder(dot)clockworkmod(dot)com/ ...
This allows people to build recovery but then there are details tht are required and catch me no balls haha... Example lik recovery.fstab, graphics.c which I think this should somehow that are needed for the tool to work properly before the CWM recovery can be generated. I think this is similar to the thread -> showthread.php?t=2285898tht someone has tried.
tanrsquare said:
Hey, doarmga... I'm quite agree with u. A CWM is quite an essential for customizing ROMs, without it, ODIN will be needed if there are going to be problems, and that's bad as it increases the binary counter... omg.
Me too, am one of the guys looking ard for i8730 recovery which is stable and usable, but I can predict tht none exists yet currently. I have search the web as well as XDA and I came to this site: builder(dot)clockworkmod(dot)com/ ...
This allows people to build recovery but then there are details tht are required and catch me no balls haha... Example lik recovery.fstab, graphics.c which I think this should somehow that are needed for the tool to work properly before the CWM recovery can be generated. I think this is similar to the thread -> showthread.php?t=2285898tht someone has tried.
Click to expand...
Click to collapse
You can obtain a recovery.fstab when you create your own CWM online then snooping around inside the downloaded zip file. Also there is the existence of a vold.fstab but I don't think that would be of any help.
About the binary counter, why don't you use TriangleAway? I can confirm it works.
P.S. LOL I never knew someone would actually read my recovery thread, let alone quote it. Heh. Thanks, people.
Sent from my GT-I8730 using xda app-developers app
hello, in a couple of weeks i will get this phone, i have one question, how is the display? i`m asking because of the low resolution on a big screen.
Ok, now some serious talk... we can get a temporary CWM recovery, sadly some samsung phones have the recovery partition on the kernel, so you need to build a new kernel with CWM, sadly i am not a kernel developer, and i don`t have to much knowledge. For overclock we need a custom kernel... the only thing i know is to build roms, but first we need a custom recovery like CWM or TWRP. I think i can make a temporary CWM but more tests i will make when my phone will get to me
About the screen
petraru1 said:
hello, in a couple of weeks i will get this phone, i have one question, how is the display? i`m asking because of the low resolution on a big screen.
Ok, now some serious talk... we can get a temporary CWM recovery, sadly some samsung phones have the recovery partition on the kernel, so you need to build a new kernel with CWM, sadly i am not a kernel developer, and i don`t have to much knowledge. For overclock we need a custom kernel... the only thing i know is to build roms, but first we need a custom recovery like CWM or TWRP. I think i can make a temporary CWM but more tests i will make when my phone will get to me
Click to expand...
Click to collapse
For the screen, overall looks Ookaayy is what I can say. It may not be as sharp as those high def display n colours looks better with higher brightness I felt. And yup for videos using stock player, mostly able to stretch fully, covering the whole screen except for some with weird resolution. Youtube videos mostly can cover the whole screen except for some old music videos with low resolutions, a little borders at the sides may be notice, but the top n bottoms doesn't have any. For high res like 1080p is able to cover the screen. Words n Clock n widgets seems to appear a little bigger n stretched. Gaming still fine n temple run 2 is really quite sharp that I love its graphics... :cyclops: But, then when open up a SWF game or app using an SWF player, some are unable to output full display, show only mostly the center and sides surrounding it being cut off... That's my experience about its screen but yup looks okay though. :silly:
petraru1 said:
hello, in a couple of weeks i will get this phone, i have one question, how is the display? i`m asking because of the low resolution on a big screen.
Ok, now some serious talk... we can get a temporary CWM recovery, sadly some samsung phones have the recovery partition on the kernel, so you need to build a new kernel with CWM, sadly i am not a kernel developer, and i don`t have to much knowledge. For overclock we need a custom kernel... the only thing i know is to build roms, but first we need a custom recovery like CWM or TWRP. I think i can make a temporary CWM but more tests i will make when my phone will get to me
Click to expand...
Click to collapse
Yay! Now we have another reason to not sell the phone.
P.S. )If this info helps in any way, haha) The Express I8730, like some Samsung phones, follows an mmc format. The recovery partition is /dev/block/mmcblk0p18 (so if I want to flash a custom recovery.img, all I have to do is pull up a terminal and type
Code:
su
dd if=/storage/extSdCard/recovery.img of=/dev/block/mmcblk0p18
* In this example, I located my img on the external SD. If yours is on the internal then use /sdcard instead.
Resolution is 480x800.
tanrsquare said:
For the screen, overall looks Ookaayy is what I can say. It may not be as sharp as those high def display n colours looks better with higher brightness I felt. And yup for videos using stock player, mostly able to stretch fully, covering the whole screen except for some with weird resolution. Youtube videos mostly can cover the whole screen except for some old music videos with low resolutions, a little borders at the sides may be notice, but the top n bottoms doesn't have any. For high res like 1080p is able to cover the screen. Words n Clock n widgets seems to appear a little bigger n stretched. Gaming still fine n temple run 2 is really quite sharp that I love its graphics... :cyclops: But, then when open up a SWF game or app using an SWF player, some are unable to output full display, show only mostly the center and sides surrounding it being cut off... That's my experience about its screen but yup looks okay though. :silly:
Click to expand...
Click to collapse
I agree. But how in the world did you get SWF games to play? Adobe says Android 4 onwards are not supported by Flash anymore.
aureljared said:
Yay! Now we have another reason to not sell the phone.
P.S. )If this info helps in any way, haha) The Express I8730, like some Samsung phones, follows an mmc format. The recovery partition is /dev/block/mmcblk0p18 (so if I want to flash a custom recovery.img, all I have to do is pull up a terminal and type
Code:
su
dd if=/storage/extSdCard/recovery.img of=/dev/block/mmcblk0p18
* In this example, I located my img on the external SD. If yours is on the internal then use /sdcard instead.
Resolution is 480x800.
I agree. But how in the world did you get SWF games to play? Adobe says Android 4 onwards are not supported by Flash anymore.
Click to expand...
Click to collapse
you can still install adobe flash player apk, just search here on xda
on my s advance Kernel and recovery (stock or custom) are in the same partition. So they must come in package, some other phones can install it separatly, because it is not connected to kernel partition. Until i get my hands on the phone i can`t be sure, but a temporary recovery is posible on stock kernel, what temp recovery means? after you reboot you lose the CWM, but for example if u make a back-up after you reflash CWM you can restore your backup.
Don`t get your hopes too high about CM, it requires allot of knowledge, in my s advance is a team of 8 developer... and they dont have yet a stable release. I can look into it but it will take time. What i can develop more easy? a ROM based on stock witch will have 0 bugs , but first CWM
Regarding CWM could someone provide me recovery.fstab? using root browser it can be found in the etc folder.
Flash on JB; about the screen.
I've searched google about flash on android 4.1 and there are quite a handful of tutorials about it. Can't post links yet but if you google it, it will show up. Basically you have to download a flash apk located somewhere on xda and install it. Also, you need a browser with flash support such as Boat browser, Dolphin or Firefox. (Chrome and the standard android 4.1 browser don't allow flash at all.)
About the screen i can honestly say that even though it has the exact same resolution as my "old" Galaxy S Plus, it looks crisper on the 4.5 display on the Express. Don't know how they managed to do this, maybe something to do with the updated pentile matrix found in SuperAMOLED Plus (3 subpixels per pixel vs. 2 subpixels and a shared one between two adjacent pixels in the "old" SAMOLED).
doarmga said:
I've searched google about flash on android 4.1 and there are quite a handful of tutorials about it. Can't post links yet but if you google it, it will show up. Basically you have to download a flash apk located somewhere on xda and install it. Also, you need a browser with flash support such as Boat browser, Dolphin or Firefox. (Chrome and the standard android 4.1 browser don't allow flash at all.)
About the screen i can honestly say that even though it has the exact same resolution as my "old" Galaxy S Plus, it looks crisper on the 4.5 display on the Express. Don't know how they managed to do this, maybe something to do with the updated pentile matrix found in SuperAMOLED Plus (3 subpixels per pixel vs. 2 subpixels and a shared one between two adjacent pixels in the "old" SAMOLED).
Click to expand...
Click to collapse
Thanks a lot, I managed to find the APK. It does look crisper, but the only reason i have for Flash is Flash games. And Opera Classic has built-in Flash, so I don't need to worry about my browser.
Sent from my GT-I8730 using xda app-developers app
Regarding recovery.fstab
petraru1 said:
but first CWM
Regarding CWM could someone provide me recovery.fstab? using root browser it can be found in the etc folder.
Click to expand...
Click to collapse
Errmmm... I had jus send my phone for repair becos of some gyro issue... I wonder anybody encounter this is tht about the 'Motion' feature in the Settings. When I activates it, the sensor jus keep moving to the right that I dun even have to move the device haha... This cause the pic in Gallery to move constantly and icon in main menu to jus keep moving. Strange thing is that it happens occasionally like let's say 1 wk, 7 days, about less than 3 days hav this prob, then the rest of the days works normally, in other words functionable n this keeps repeating. It makes me cracking my mind if it's a hardware or software issue n tis is jus weird... I tried lots of times on calibration n restarting device but still no luck. Or maybe jus for a short while haha... I heard of no sound after flashing another stock rom, but mine's jus the original stock. Ok... Sry about the nagging but mayb jus to share abit. :crying:
And for recovery.fstab file, I'll retrieve n upload it after collection of the phone... maybe in a few day's time sry abt that!
tanrsquare said:
Errmmm... I had jus send my phone for repair becos of some gyro issue... I wonder anybody encounter this is tht about the 'Motion' feature in the Settings. When I activates it, the sensor jus keep moving to the right that I dun even have to move the device haha... This cause the pic in Gallery to move constantly and icon in main menu to jus keep moving. Strange thing is that it happens occasionally like let's say 1 wk, 7 days, about less than 3 days hav this prob, then the rest of the days works normally, in other words functionable n this keeps repeating. It makes me cracking my mind if it's a hardware or software issue n tis is jus weird... I tried lots of times on calibration n restarting device but still no luck. Or maybe jus for a short while haha... I heard of no sound after flashing another stock rom, but mine's jus the original stock. Ok... Sry about the nagging but mayb jus to share abit. :crying:
And for recovery.fstab file, I'll retrieve n upload it after collection of the phone... maybe in a few day's time sry abt that!
Click to expand...
Click to collapse
thanks, i managed to find it
if someone can test temporary CWM http://d-h.st/OBd
just put update.zip to sdcard, reboot to stock recovery, flash update from external storage, then reboot and hold down buttons for recovery.
tomorrow morning i will finish negotiating with my carrier, if all ends well, next week i will have the phone the only down side is after next week i will go on holiday with my family for 10 days
p.s how does this phone performs on high end games like modern combat 4, nfs most wanted, gta vice city, the dark knight rises?
from what i read on the internet the Qualcomm MSM8930 Snapdragon 400 Dual-core 1.2 GHz Krait and Adreno 305 is very good, it can beat some quad core CPUs i saw a benchmark and the scores are allmost like the S3 (because of screen resolution, but still, pretty slick )
Are there any current WIP roms for this specific device. I remember searching the entire forum for this phone a couple months back and there was little to no information, though the motochopper guide existed besides for the obvious root privileges there were no custom roms for the phone.
Fire98251 said:
Are there any current WIP roms for this specific device. I remember searching the entire forum for this phone a couple months back and there was little to no information, though the motochopper guide existed besides for the obvious root privileges there were no custom roms for the phone.
Click to expand...
Click to collapse
not yet...
petraru1 said:
not yet...
Click to expand...
Click to collapse
Do you own the phone?
petraru1 said:
thanks, i managed to find it
if someone can test temporary CWM http://d-h.st/OBd
just put update.zip to sdcard, reboot to stock recovery, flash update from external storage, then reboot and hold down buttons for recovery.
tomorrow morning i will finish negotiating with my carrier, if all ends well, next week i will have the phone the only down side is after next week i will go on holiday with my family for 10 days
p.s how does this phone performs on high end games like modern combat 4, nfs most wanted, gta vice city, the dark knight rises?
from what i read on the internet the Qualcomm MSM8930 Snapdragon 400 Dual-core 1.2 GHz Krait and Adreno 305 is very good, it can beat some quad core CPUs i saw a benchmark and the scores are allmost like the S3 (because of screen resolution, but still, pretty slick )
Click to expand...
Click to collapse
Yay! Am trying it now.
Sent from my GT-I8730 using xda app-developers app
SO it seems there is no custom recovery for the device... I just got it a few days ago thinking WOW what a good phone and it also looks like the S3.. All of my phones have either been jailbroken or rooted. Turns out the phone has no recovery section. It's in the Kernel, so therefor you will need to build a whole new kernel.. I would love to have this device rooted with a recovery to install roms and such. I will also love to donate for the project if anyone does it.
ok, good news, i signed the contract with my carrier so the phone will get to me next week

Camera 2 "Software Update" Received 12/20/2014

Woke up this morning to my Galaxy Camera 2 claiming it was downloading a new software update (~130mb). Of course, there's no mention anywhere in the update process for what is included in this update, but I can definitely tell you that it's not Kitkat (sadly). Unfortunately, I didn't check version numbers prior to accepting the update (sorry), but here's the version numbers after the update:
Build Number:
JSS15J.GC200XXUCNK4
Kernel version:
3.0.31-2807772
[email protected] #1
Sat Nov 29 15:55:43 KST 2014
That's the same Build Number we've had since like April 2014, but the kernel definitely seems to have been updated. Maybe they finally fixed the loss of Google account settings issue??? I appreciate updates, but I really wish they would inform the customer better on what these updates fixed.
Ironically, for the first time in a long time, my Camera 2 had lost its Google Account settings when I turned it on this morning....haha.
Oh, I reside in Florida, USA. Not sure who else in the world is receiving the update, but according to SamMobile.com the Camera 2 update was hitting other locations around the globe starting 12/18/2014, but there's no mention of it hitting the USA at all.
Need to know if it's root able.
cantenna said:
Need to know if it's root able.
Click to expand...
Click to collapse
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Well, it's been almost a week since this update and it's also been a week of heavy Camera 2 use with the holidays. I haven't lost Google settings even once.
Thus far my camera hasn't lost my Google accounts, and by now it surely would have happened
Sent from my Nexus 9 using Tapatalk
internetpilot said:
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Click to expand...
Click to collapse
Eh...
I didn't waste my time getting the Galaxy Camera 2, just got the One.
I understand your stress though.
Someone needs a swift kick in the butt so we can get development going for both devices.
Sent from my LG-P920 using XDA Free mobile app
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
mark2410 said:
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
Click to expand...
Click to collapse
Assuming you do get it, could we transfer it over to the Galaxy Camera One, Wi-Fi Edition?
I don't like to be the rude one. But at this point, someone has to help root the Wi-Fi Only version, and come up with a Custom Recovery.
Not only this, but we need to see Devs, but we've got people sitting and pointing fingers instead.
I wanna see a ROM putting us all on a better version, or something more come to all the cameras.
Sent from my LG-P920 using XDA Free mobile app
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
mark2410 said:
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
Click to expand...
Click to collapse
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Sent from my EK-GC110 using XDA Free mobile app
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
cantenna said:
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
Click to expand...
Click to collapse
Why would anyone want to put 128GB of apps on a camera? I mean, a tablet or phone, okay...but a camera? I just don't really see the practical purpose for that. The biggest storage hog on my tablet/phone is music and movies, and neither of those require the device to be rooted to store them on the external SD card.
Again, with the way Samsung is really clamping down on not allowing OTA's to be delivered to even just rooted devices, and with the basically non-existent development support for this device, I won't be rooting it until I'm 100% certain that there's no OTA update coming for it, and even then I would only root it if someone put out a reliable custom Kitkat or Lollipop ROM for it. Honestly, if Samsung won't update it, then I'm really not holding my breath that some 3rd-party dev ever will.
Ouya-XD said:
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Click to expand...
Click to collapse
It would be a heckuva lot easier to port a Camera 2 ROM over to the Camera 1 (rather than develop a ROM from scratch for either camera model), but even that hasn't been done. I don't think there's ever going to be any original development on these devices (like a CM11 or CM12). Developing ROMs isn't terribly difficult, but it's not easy either, especially not on a device that is so driver dependent like these cameras are. Just about every Android device I've owned (phone or tablet) has problems with the camera not working in some way (if not completely) on any original development project. What good is a camera with the latest Android OS if it causes the camera function not to work or even not work reliably?
I think we need to face it, folks -- these cameras are pretty much as-is. At best we're highly dependent on whatever Samsung gives us.
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
hmmm i get your point but for me, the camera is a camera. ive got a tablet for tablety things, a phone for phoney things so what i want is camera focused and to have dropbox autoupload everything nicely.
thats the anly reasen im so fussed that i want it to get lollipop as it should then get RAW capabilities. while i realise it may not happen i will vote with my wallet. this is my first real samsung device (galaxy nexus doesnt count) and while i love oled screens and removable batteries if samsung abandon the camera, well i will abandon them. its really that simple, if they wont support devices going forward then i wont buy any other android devices from them.
if only google put out a Nexus Camera.
NK4 and rooting
I just finished the upgrade to NK4. I was trying to keep root through survival mode in Superuser Pro, but I ended up having to reroot. The upgrade via kies took about a hour. I attempted to re-establish root via Superuser but was unable to do so. I ODIN'ed the CF-autoroot onto the camera and reinstalled Superuser. I now have a NK4 rooted camera.
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
So, if you're rooted on NC2, fear not. The water's OK over here on NK4.
cantenna said:
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
Click to expand...
Click to collapse
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
cantenna said:
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
Click to expand...
Click to collapse
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
10amla said:
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
Click to expand...
Click to collapse
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
internetpilot said:
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
Click to expand...
Click to collapse
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
cantenna said:
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
Click to expand...
Click to collapse
If you think a multi element autofocus mechanical extending zoom lens and an electronic shutter are never going to fail, then you better start preparing yourself for disappointment in about 2 years. LOL.
My three $25 AndroidTV boxes have been working great for years, running Netflix and Amazon Prime video since day one that I bought them. They're also running Kitkat even though they started out on Gingerbread.
10amla said:
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
Click to expand...
Click to collapse
I'm pretty sure that all of my Samsung devices have been rooted and ROMed using Odin. My first Android device was a HTC EVO 4G, which solely used custom recoveries (unless you just like going back to the dark years of ADB), so the first couple of times I asked devs for a flashable zip, I was all but excommunicated from the XDA forum for such blasphemy. Everyone here seems to do just about everything via Odin, so I don't really sweat not having a custom recovery. Most things that can go wrong (bootloops, soft-bricks, etc.) when mucking around flashing devices are solved via Odin anyway.

Updated tablets

Just left my local Walmart and seen they had the new versions out already. 99$ for the 8 inch and 129$ for the 10.1. Anyone get one yet? If you do let us know how the performance compares to the previous tablets
twfs said:
Just left my local Walmart and seen they had the new versions out already. 99$ for the 8 inch and 129$ for the 10.1. Anyone get one yet? If you do let us know how the performance compares to the previous tablets
Click to expand...
Click to collapse
New Amazon HD 8 comes out June 3rd starting at $90 US. Looks like better specs than the new Onns. Downside is dealing with FireOS as a bootloader unlock is unlikely.
Anybody have any actual specs on the display resolutions for both the 8 and the 10.1?
GilmourD3 said:
Anybody have any actual specs on the display resolutions for both the 8 and the 10.1?
Click to expand...
Click to collapse
I just bought the 8", 1280x800
Update
twfs said:
Just left my local Walmart and seen they had the new versions out already. 99$ for the 8 inch and 129$ for the 10.1. Anyone get one yet? If you do let us know how the performance compares to the previous tablets
Click to expand...
Click to collapse
Just purchased the 10." version and has updated to the latest Android 10 right out of the box.
Good look on the screen and rapid page load on Chrome.
Will try rooting it here shortly and report back.
Update: Latest A 10 version:Security patch level 5 March 2020
Device Info HW indicates resolution: 1200 x 1920
kerry49 said:
Just purchased the 10." version and has updated to the latest Android 10 right out of the box.
Good look on the screen and rapid page load on Chrome.
Will try rooting it here shortly and report back.
Update: Latest A 10 version:Security patch level 5 March 2020
Device Info HW indicates resolution: 1200 x 1920
Click to expand...
Click to collapse
Kinda curious about battery life too. They are advertising quite a improvement in that category
twfs said:
Kinda curious about battery life too. They are advertising quite a improvement in that category
Click to expand...
Click to collapse
Give me a couple of days on that and I'll let you know...
I will say that so far on a scale of 1 to 10, I'll give it an 8.5 to 9. Seems well worth the $129.00 price for what I'm going to use it!
Is the bootloader unlocked on the new Onn tablets?
Bootloader lock
pharpe said:
Is the bootloader unlocked on the new Onn tablets?
Click to expand...
Click to collapse
I have enabled it in dev options but have not gotten to run adb commands on the bootloader yet. Maybe tomorrow or this weekend.
I am really hoping to at least root it even if I can't install twrp in recovery!
Will advise ....
Android 10 is a bit different when it comes to flashing
Hopefully you can unlock bootloader and grab boot.img and patch it with Magisk, and flash under recovery like fastbootd even flashing command stays the same
Unlocking bootloader
Unfortunately I can not get Win 7 to recognize the tablet. I have followed the instructions but updating MTK driver installation keeps complaining of lack of .inf file.
May try to access bootloader from Debian and see if that works.
Update on battery life .... I have not plugged it in since yesterday and have used it lightly. Still showing 80% so might have to run a movie to tax it.
Update:
I am unable to access the tablet via adb in Win 7 or Debian. Can't get Debian to recognize the unit in fastboot. Yield to those more knowledgeable
Update 2:
Ran this heavy this weekend and it went to 20% battery after 7 hours so not too bad. I still have not gotten win 7 to recognize the tablet in fastboot. This may be the first Android (10) that I own that isn't rooted. The damned ads are killin me!!!
Update 3 (4 June 20):
I have given up on rooting for fear of bricking the tablet. I have, however, installed the Blokada app and it at least blocks the annoying ad images on web browsers. Downside ... the ad text shows but I can live with that.
Battery life is still excellent so I'm gonna leave it "as is" for the moment.
So I didn't realize this was the latest tablet and attempted to root it via the older 8" tablet boot.img. The tablet won't boot now, does any have the stock boot.img? thanks!
pendleton_33312 said:
So I didn't realize this was the latest tablet and attempted to root it via the older 8" tablet boot.img. The tablet won't boot now, does any have the stock boot.img? thanks!
Click to expand...
Click to collapse
Any luck finding any stock images for these tablets? I have the 10 inch 2020 tablet and have AOSP's generic images on the tablet -- I thought I could pull the boot.img from that tablet (both prior to and after rooting it with magisk) and use it on another one of these ONN tablets...
... but I seemed to caused the tablet not to boot (can still get into fastboot/recovery).
I just wanted to pull the stock image from it so I could reflash my tablet and return this one, but looks like it might get returned in this state. I reached out to Walmart to see if they would share the stock firmware and they asked for my email but I haven't heard anything yet.
Fastboot works 10.1 ver 3gb mem
mingkee said:
Android 10 is a bit different when it comes to flashing
Hopefully you can unlock bootloader and grab boot.img and patch it with Magisk, and flash under recovery like fastbootd even flashing command stays the same
Click to expand...
Click to collapse
Adb doesn't work, but fastboot works
I bought it yesterday 10.1 inch, and to me it feels ok 3 gb, , and I'm able to get unlocked , fastboot , but I had different adbs installed on my PC , first one wouldn't unlock it, second one would...so I even see it on booot, your tablet can't be trusted error , but I cannot for the life of me get adb to recognize it..tried every driver I found, Linux Ubuntu as well, all fastboot commands seem to work fine, strange! If someone helps me find a stock image for it, i will will majisk the boot.img, and push it,, but I can't find it.. adb devices never show anything tried win7, Linux Ubuntu laptop, and win 10..
It scrolls strange with chrome, on internet , but not terrible, feels nice to me overall, help me find stock, and I will post screenshots , and tutorial but that's where I'm at, I have no need for twrp, just want root to remove these 3 or 3
4 Walmart apps....thanks...
Bootloader
jdills1196 said:
Any luck finding any stock images for these tablets? I have the 10 inch 2020 tablet and have AOSP's generic images on the tablet -- I thought I could pull the boot.img from that tablet (both prior to and after rooting it with magisk) and use it on another one of these ONN tablets...
... but I seemed to caused the tablet not to boot (can still get into fastboot/recovery).
I just wanted to pull the stock image from it so I could reflash my tablet and return this one, but looks like it might get returned in this state. I reached out to Walmart to see if they would share the stock firmware and they asked for my email but I haven't heard anything yet.
Click to expand...
Click to collapse
Here is a vid so you know I'm not a troll
Bootloader unlock proof:
https drive.google.com /file/d/1eKFrWD6FtkzwD0NC_aT6Ri3VovXZiJMF/view?usp=drivesdk
(I'm a new junior member, so I can't link the video url, you will have to rename the above link - properly)
Also found you can disable and remove Walmart adds, which is a plus, still cant get adb to recognize, refer to my last post, but can unlock bootloader: fastboot worked for me, so patiently waiting for a stock image, as I can't backup my boot.img without adb not detecting the device..seems doesn't matter if rooted or not as my main goal was to disable and hide Walmart shortcuts(which it lets you do in the Apps), I don't see adds on 10.1 in chrome , as the last guy said, maybe that's an 8 issue. Google browser is buggy though..overall I like it..but I'm no gamer,hope that helped someone
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Lastly, if you have big hands it feels amazing for the size, if you set to auto rotate, Portrait is how I like it (then flip when you watch YouTube), but if you have small hands and want to type, I think it's better not to buy this device...not designed right for small hands and on screen typing....just my Take
Just wanted to add my 2p to this thread:
Got this tablet a few weeks ago and have been using it fairly regularly. I can say with some certainty that, for $130, the 10.1" tablet is fantastic value for money. I say the 10.1" because it has the benefit of having 3GB of RAM. I would be hesitant to purchase the 8" as it only has 2GB.
The screen is very nice, battery life has been adequate for my uses (do not consider that an in-depth analysis), and the MTK chip inside the thing has hardware decoding for almost all major codecs. I did have to switch to SW decoding for some 10bit HEVC content I was watching last weekend, but the tablet actually handled that really well, and I didn't notice any hitches or slowdown even with the content being 1080p.
One downside, however, is that this is definitely a budget device when it comes to CPU performance. For the vast majority of thing you don't notice, but for heavier sites (such as, for e.g., Autotrader) really slow things to a crawl. Those are definitely the exception rather than the rule, though, with Autotrader being the only one that impacted me personally. And even then, there is an app for that.
Even though I am someone who used to root these devices a lot, all of the features present in Android 10 means I really don't feel the need to do that anymore. Any built-in apps can be easily "disabled", even if they can't be uninstalled (but with 32GB of onboard storage, I really don't think that would effect anyone that much). This is also entirely stock Android, so that's nice compared to the competing Fire tablets.
One thing that I do wish could be easily disabled is the little "Walmart logo" navigation icon. Again, all bloat can be removed so it's really nothing more than an eyesore. But I am exceptionally picky with that kind of stuff, so if that is the only thing I have to complain about, I will consider this tablet in good shape!
Agree with u!
I just think it feels amazing, and hate fireos, but agree with you, I'm happy with Netflix and YouTube and duolingo, so I don't know the others..and language learning audio books. ....doesn't need rooted,. But, I like making backups and making it mem light as possible..gonna try to use that FWUL to get Adb , working, still can load image.bin for root, whenever we find a stock, as fastboot works.. but even if not, this feels solid, once you disable like 6 crappy programs ..I really like it, even if it never gets rooted..I disabled all Walmart apps and a couple others like YouTube music, and went light on Google play store, no updates/sync running , happy with it.
9/10 for what I need it for..once you get used to typing and scrolling, and ooohh that sweet battery life!
I was just hoping I could find a stock image before return policy.
Update Walmart button hide Android 10
Hide Walmart button by enabling "Gesture Navigation" Android 10 fearure , FYI, takes a few min to get used too, dragging up,, but issue gone, and I prefer this swipe now better...
I knew you said it bothered u
Army701 said:
Hide Walmart button by enabling "Gesture Navigation" Android 10 fearure , FYI, takes a few min to get used too, dragging up,, but issue gone, and I prefer this swipe now better...
I knew you said it bothered u
Click to expand...
Click to collapse
Stock boot and recovery images are in the stock images thread, I posted the 10 pro last night.
I can't get root on either the 8 or 10 pro. Patching the boot image doesn't work, device bootloops. If it's a non A/B, system as root device, then I'd patch Recovery and boot that way, but it didn't work either.
I'm not sure how to get root working.
Is bootloader unlocked ?
And , did you disable secure boot first , with fastboot? I'll help you as much as I can
---------- Post added at 02:48 PM ---------- Previous post was at 02:41 PM ----------
try to flash a magisk patched boot.img as:
fastboot --disable-verification , in front of your patched boot.img (or whatever it's named mijisk edited)**" also don't know exact command offhand , something similar?
If I boot in recovery, I see secure boot enabled
Also, are you able to go back to stock? Or is it all ****ed up now
Keep me updated as I got a week left to return it, also thinking of other solutions...

FireHD 10 Suez { Speed of Lineage vs Stock } -- Processing.org sketches

Hi,
I have a couple of these 2017 fire HD tablets all rooted and experimenting with various OS's on them.
I've been working on a processing.org sketch on android for a couple years now and running into some unique FPS issues.
When I run Lineage 2022 May edition, the app runs at roughly ~22FPS
When I run the same app on 5.6.2.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip I get roughly ~40 FPS.
**Side note, I built a quick sketch to post here with source code and APK but when I run it on both tablets, they are both 60FPS.. which leads me to believe something else is going on weird. The sketch just dumps a bunch of circles on the screen and displays FPS in biggen font.
Is there anything I can do to provide someone details for research or help me in troubleshooting?
I'm tempted to try a old lineage build like
[discontinued][ROM][unlocked][suez] Lineage-12.1 [05 MAY 2020]​Generally just work my way up to later and later builds and figure out where it broke and stay there.
Technically I don't NEED to run lineage, but I would like really any version of any OS for the fire HD that runs quickly. It doesn't need to be the latest.
I just need something with some customizability.. run app on USB power, auto power off tablet when USB power is removed... I haven't got that far yet.. but my requirements are minor.
Additionally.
Could someone provide some links to all the various os packages I can try installing?.. Not sure if it would be helpful, but a pinned post with just url's to all?
So far I have seen latest MAY 2022 release of Lineage, then these hacked older versions of the fire OS software. Is there any others?? Please link below I'd like to try them out.
Thank you,
Take care.
any news here ?
I haven't seen anything. I was just scooping up all OS releases and running a test sketch on each one.. I can publish a simple APK file if people want to try this out. But really there are better benchmarking apps out there, mine was just simple like draw a bunch of circles on a screen and print the fps.
Thanks... I'm going to install Lineage, so if you want to me compare....
targa said:
Thanks... I'm going to install Lineage, so if you want to me compare....
Click to expand...
Click to collapse
Hi Targa,
I made a post on Reddit a while ago with the same subject and realized I didn't update the thread here.
This is what I tried.
5.6.2.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip I get roughly ~40 FPS.
lineage-12.1-20200505-UNOFFICIAL-suez.zip ~locked at 44FPS. oldy thou.
lineage-14.1-20190926-UNOFFICIAL-suez.zip ~locked at ~48 FPS, less oldy.
*These aren't links.
As far as the OS is concerned, with what I am using the tablet for, I really do not care which one to use.
I have some basic requirements in which I'm guessing that any of them will work.
*I need a method to power on the device when USB power is applied.
* This app would auto start that I specify.
*When usb power is removed, the tablet would turn off.
I'm putting this in a car and writing some custom processing.org sketch and since the tablet is in a 3d printed caddy like thing, I don't have easy access to the power button and need things to be automated, I also don't want to have to touch the screen to launch something. Perhaps wishful thinking.
Thanks.
crap, I bricked by tab while trying to bring it to Lineage... Guess I need to open it now.
Thanks.
Is it the waiting for bootrom message? if it is plug in the usb leave it at the waiting for bootrom message on the terminal and hold the power button on the tab, it should take 5-15 seconds and it will then just say "remove short" which in the scheme of things there was no short. just hit enter and continue. I've done 3 of these tablets.
Yes, I managed, thanks for the hint (even if I already managed before, it was described in one of the threads).
targa said:
Yes, I managed, thanks for the hint (even if I already managed before, it was described in one of the threads).
Click to expand...
Click to collapse
No worries, I think a lot of times its hard to write guides. I tend to be overly verbose when explaining things to help with a lot of the back and forth. Habit I guess..
likwidchz said:
Hi Targa,
I made a post on Reddit a while ago with the same subject and realized I didn't update the thread here.
This is what I tried.
5.6.2.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip I get roughly ~40 FPS.
lineage-12.1-20200505-UNOFFICIAL-suez.zip ~locked at 44FPS. oldy thou.
lineage-14.1-20190926-UNOFFICIAL-suez.zip ~locked at ~48 FPS, less oldy.
*These aren't links.
As far as the OS is concerned, with what I am using the tablet for, I really do not care which one to use.
I have some basic requirements in which I'm guessing that any of them will work.
*I need a method to power on the device when USB power is applied.
* This app would auto start that I specify.
*When usb power is removed, the tablet would turn off.
I'm putting this in a car and writing some custom processing.org sketch and since the tablet is in a 3d printed caddy like thing, I don't have easy access to the power button and need things to be automated, I also don't want to have to touch the screen to launch something. Perhaps wishful thinking.
Thanks.
Click to expand...
Click to collapse
Did you find the "perfect" Software for your hardware?
@targa which Lineage OS version did you find to be more stable? I am going to change from stock because of compatibility issues... My primary requirement is reading and watching, after getting used to higher refresh rate displays I feel its too odd to use something with lower framerates, so I want to know more about it. also I bricked my suez(FireHD 10)... and if someone can help me a lil bit please feel free to send a message.
Rex218 said:
@targa which Lineage OS version did you find to be more stable? I am going to change from stock because of compatibility issues... My primary requirement is reading and watching, after getting used to higher refresh rate displays I feel its too odd to use something with lower framerates, so I want to know more about it. also I bricked my suez(FireHD 10)... and if someone can help me a lil bit please feel free to send a message.
Click to expand...
Click to collapse
Hi there,
Honestly, I would try them all. My only test scenario was a single app I am making for a personal project.
My requirements were pretty low. Wireless needs to work, it needs to not drain power and decent frame rate in my app. Sound isnt required.
My results were pretty mixed and when it boiled down to it. It almost didn't make much of a difference. Because I don't need a lot of features, I would probably stick with the oldest release, and the sound patch to allow head phones to work.
Which is why I would say try them all. The latest does not always mean the best in my opinion. Feel free to prove me wrong here, I am up for discussion.
Thank you,
Take care.
Hi,
my tablet is now on Lineage and I'm happy with it. But my use cases aren't really extensive, I basically use it so that my kids can watch videos and earplays and some games. But for sure it's a lot better and newer than FireOS. I believe headphones did work so far.

Categories

Resources