Related
Hi guys,
I've brought up the question in a few places (on here and elsewhere) but it hasn't been a topic of discussion anywhere yet.
With the current flurry of activity in Defy development, does anyone know whether or not eFUSE is enabled on the Defy? I think this fact may be very critical in determining the future of the device. Cooked ROMs will still be limited by whatever the latest version Moto have released if eFUSE is active.
Some small part of me hopes that it is mysteriously disabled, like on the Droid..
This is what the (US?) law thinks about playing with "your" phone.
It’s worth noting that the jailbreak ruling does not force Apple or other handset makers to remove copy protection from their software. Rather, those users who do choose to circumvent the protections will not be subject to criminal prosecution for the act of circumvention. In addition, the ruling only provides for jailbreaking for the use of legally-acquired software, meaning that users cannot use it as a defense for installing pirated applications.
Click to expand...
Click to collapse
I doubt eFuse is disabled - Motorola wants you to buy a new handset if you want new software. There are too few people who woudn't buy the phone because it's locked and there is no other reason to provide an unlocked phone.
They also don't want to let others profit from updating their phones, but a planned 2011Q2 update (to 2.2) for the buggy Defy is not competitive.
Ya know what they say "Motorola screw me once shame on you screw me twice ain't going to happen".
Well then, fingers crossed they "accidentally" left it turned off like in the Droid..
Since eFUSE really doesn't sound like it's ever going to get cracked.
Passa91 said:
Well then, fingers crossed they "accidentally" left it turned off like in the Droid..
Click to expand...
Click to collapse
I'm not sure it was an accident.
The whole point about eFUSE is that it's a chip that bricks the handset if it detects the wrong software on it.
Whilst the Motorola handsets have this chip, a fact that came out around the time of the Droid X's release, I was under the impression that it wasn't enabled.
I know there's an encrypted bootloader or something that some Motorola handsets have but I'm sure I read in one of the other sections that the Defy didn't have this.
Or maybe I'm confusing myself again...
It doesn't brick the handset, but it prevents unsigned kernels from running on the CPU I believe..
The Droid X was not the first Moto to sport eFUSE. The Milestone (GSM version of the Droid) was the first one with eFUSE enabled. The only reason they've got a Cyanogen 2.2 kernel ROM right now is because a signed Froyo ROM from Moto was leaked.
Well, if that's what the eFuse chip does, then according to this, it's apparently not enabled on the Defy.
Hey everyone!
I've been looking at the A100 lately, as I have the ability to obtain one (new) for $75 and change (after a credit with the store). However, after reading this thread a bit, I'm concerned about the emmc issue.
Has Acer released any updated models that don't have this issue, do they all have this issue (at some point)? It's the only reason I would avoid it and look at different models. Is there an assembly date to watch for? lol I'd like to get one, but would rather avoid an issue like this, as I enjoy modding devices and don't want to run into warranty issues trying to have faulty tech replaced.
Any help/clarification would be greatly appreciated!
heX79 said:
Hey everyone!
I've been looking at the A100 lately, as I have the ability to obtain one (new) for $75 and change (after a credit with the store). However, after reading this thread a bit, I'm concerned about the emmc issue.
Has Acer released any updated models that don't have this issue, do they all have this issue (at some point)? It's the only reason I would avoid it and look at different models. Is there an assembly date to watch for? lol I'd like to get one, but would rather avoid an issue like this, as I enjoy modding devices and don't want to run into warranty issues trying to have faulty tech replaced.
Any help/clarification would be greatly appreciated!
Click to expand...
Click to collapse
As far as we can tell they all have the same run of emmc memory, so in theory are all prone to it. Some protection can be found in the godmachine kernels and recovery, though. Mine hasn't bricked a second time since using a modified version of his kernels.
pio_masaki said:
As far as we can tell they all have the same run of emmc memory, so in theory are all prone to it. Some protection can be found in the godmachine kernels and recovery, though. Mine hasn't bricked a second time since using a modified version of his kernels.
Click to expand...
Click to collapse
Thanks for the quick response! I've done some searching but can't seem to find any info on godmachine's recovery (unless I mistakenly overlooked it)? I can find his kernel (v2.0) and it appears to be installed via TWRP (which is fine).
This leaves me to assume that after unlocking the bootloader via the A200 replacement, I should just install TWRP, then flash godmachines kernel? (all this of course, after doing the ICS upgrade out of the box).
This is what I told a friend of mine who was thinking of getting one:
Depending on how much credit you are using, I would not spend more than $120 total for an A100 with all the new 7" tablets coming out with xmas and black friday on the way. I highly doubt you will get any more updates from acer with the new tablets they are releasing.
Pro:
Tegra2 chipset is great. ICS/JB runs really well. HDMI out works so this tablet acts as my portable media player (netflix, hulu, streaming from nas) to keep the kids busy. Games run well.
Con:
Emmc issue, bad viewing angle (even if it is only one really bad angle, the others are not so great either), low resolution, SOD, bad battery time (at least it charges really fast though), and worst of all, the touch screen issues. There are just some spots on the tablet that it takes 3-4 tries to work. build.prop also needs to be changed to show A500 for some games to be available.
As for development here on xda (with respect to pio_masaki and his private works) its safe to say that its pretty much dead. Good news is that the CM10 we have works almost flawlessly and Flexreaper rom is as solid as it gets.
Thanks for the feedback. I think, for now, I'll wait till the holidays arrive and see if other models come down in price. The Tegra 2 and dual core seemed a pretty decent combo for the price. The emmc issue is a complete turn-off, and was an absolute downer to read! But there is some possible hope for that with godmachines kernel.
I haven't read into it enough to have discovered the touch screen issues you mentioned, that is also going in the turn-off section.
Maybe I'll see what happens price wise with the Nexus 7 in December.
Thanks for the quick replies and helpful info! I'm still tempted, but will hold off on a purchase for now.
heX79 said:
Thanks for the quick response! I've done some searching but can't seem to find any info on godmachine's recovery (unless I mistakenly overlooked it)? I can find his kernel (v2.0) and it appears to be installed via TWRP (which is fine).
This leaves me to assume that after unlocking the bootloader via the A200 replacement, I should just install TWRP, then flash godmachines kernel? (all this of course, after doing the ICS upgrade out of the box).
Click to expand...
Click to collapse
I let all the OTA ICS updates install, then rooted, then unlocked the bootloader, then installed TWRP, I then
used TWRP to install CM10, Jelly Bean optimized Kernel for A100, and pio_masaki's Gapps all at the same time,
I hope the "disabled MMC_CAP_ERASE function" does the job. :fingers-crossed:
I have done a general search on Google and found several articles relating to this subject, but when I searched XDA I didn't find anything conclusive or useful or even informative. The Samsung Galaxy S4 was supposed to be at least a 16GB phone. To me, that means 16GB of usable space to install apps. I knew there would be some bloatware, but when I got my SGS4, I was annoyed to see that the device memory total space was only 9.72 GB, and the bloatware was installed in that space! That left me with only a measly 8GB to install my apps. So where did the other 6.28 GB go? From what I read, it was used by the "system" and hidden "Samsung recovery partitions".
Well, I do not care about recovery partitions. I would rather trust Titanium Backup and my Nandroid backups and have more usable space than have a recovery partition I can't access. I am stingy with my storage, which is at a premium on mobile devices. I like to have control over every megabyte and I don't like the manufacturer deciding how my space is used. I already got an SD card for it, but I still want that missing space back.
So here is my question; how does one re-partition or re-size the partitions of the internal memory of the Samsung Galaxy S4? I know that linux has some amazing partition editors like gparted that can re-size partitions without destroying them, and Android is based on linux, so is there anything like an "aparted"?
I think in the system partition aside from the actual OS there's an odd 2-3 gigs of temp space to be utilizing during updates via Kiev etc. Since the size of TW roms are so big it makes sense in some weird way.
However anything I've read regarding repartioning is supposed to be pretty risky procedure. A lot of us that have gone to the Google Edition rom are also stuck with the original partitions even though GE rom nearly a gig smaller than TW rom. So especially wasted space for us.
Sent from my GT-I9505G using Tapatalk 4 Beta
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
lazaro17 said:
I think in the system partition aside from the actual OS there's an odd 2-3 gigs of temp space to be utilizing during updates via Kiev etc. Since the size of TW roms are so big it makes sense in some weird way.
However anything I've read regarding repartioning is supposed to be pretty risky procedure. A lot of us that have gone to the Google Edition rom are also stuck with the original partitions even though GE rom nearly a gig smaller than TW rom. So especially wasted space for us.
Sent from my GT-I9505G using Tapatalk 4 Beta
Click to expand...
Click to collapse
See, that's exactly what I am talking about. I don't plan to ever update my stock rom via Kiev, assuming I ever update it at all, since I flashed a modified stock kernel to get root. Where did you read about repartitioning being risky? I couldn't even find that much. Is it equally risky for all devices, or do the more modern devices have more options? I also flashed the Google Edition rom hoping to get the space back, but nope! It really sucks that a non-touchwiz, non-samsung rom would still allow a wasted partition.
Zaron DarkStar said:
See, that's exactly what I am talking about. I don't plan to ever update my stock rom via Kiev, assuming I ever update it at all, since I flashed a modified stock kernel to get root. Where did you read about repartitioning being risky? I couldn't even find that much. Is it equally risky for all devices, or do the more modern devices have more options? I also flashed the Google Edition rom hoping to get the space back, but nope! It really sucks that a non-touchwiz, non-samsung rom would still allow a wasted partition.
Click to expand...
Click to collapse
In order to partition that internal memory you have to wipe it. And that means everything. System, recovery, download mode, boot loader, everything.
The connection with Odin or adb at this point would be totally housed in RAM. It would need to maintain that connection in order to complete the task of adding the new partition, adding the download mode back, adding recovery, and finally the ROM itself.
If the phone lost its connection during that process or lost power or the update process got pushed out of ram for any reason the phone would be hard bricked as there would be no way to reestablish communication with it to restart the process. You couldn't power it on or boot it to anything. It would be a $600 paper weight.
Meanwhile the alternative option is to just go buy an $8 external 16gb SD card or a $20 external 32gb SD card. That carries no risk whatsoever and expands your phone's storage well beyond the original 9gb of usable space you started with.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
In order to partition that internal memory you have to wipe it. And that means everything. System, recovery, download mode, boot loader, everything.
The connection with Odin or adb at this point would be totally housed in RAM. It would need to maintain that connection in order to complete the task of adding the new partition, adding the download mode back, adding recovery, and finally the ROM itself.
If the phone lost its connection during that process or lost power or the update process got pushed out of ram for any reason the phone would be hard bricked as there would be no way to reestablish communication with it to restart the process. You couldn't power it on or boot it to anything. It would be a $600 paper weight.
Meanwhile the alternative option is to just go buy an $8 external 16gb SD card or a $20 external 32gb SD card. That carries no risk whatsoever and expands your phone's storage well beyond the original 9gb of usable space you started with.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Thanks! And yes I also hit the thanks button . I had no idea that partitioning the internal memory was THAT risky. I am surprised nobody has come up with a better way, like how you would boot from a CD to partition your computer. Maybe a way to boot from external SD or something? It also makes me curious; if the manufacturer started with blank internal memory, how did they write the initial recovery and ROM to it in the first place? What are they able to do that we can't do?
Zaron DarkStar said:
Thanks! And yes I also hit the thanks button . I had no idea that partitioning the internal memory was THAT risky. I am surprised nobody has come up with a better way, like how you would boot from a CD to partition your computer. Maybe a way to boot from external SD or something? It also makes me curious; if the manufacturer started with blank internal memory, how did they write the initial recovery and ROM to it in the first place? What are they able to do that we can't do?
Click to expand...
Click to collapse
Your computer has a bios that exists on a saparate chip from everything else. The bios is like a pre-boot that waits for you to hit the power button, then it looks for a hard drive with an OS to get going the rest of the way. If it doesn't find a hard drive it will look to a CD ROM drive that will take the next step.
The operating sysem resides on your hard drive. So you can wipe your hard drive and the bios will at least let the computer physically turn on.
On your cell phone all that stuff resides on the same internal memory. So if you wipe it clean, it doesn't even have something like a bios that can look for a secondary boot option on an SD Card.
Samsung probably programs the memory chips on a separate machine before they even put them on the mother board. Think of an old 8 bit Nintendo. Super Mario Bros. exists entirely on the game cartridge. It's pre programed to hold the game. You then take that game cartridge (which is essentially just a memory chip on a circuit board inside the plastic case) and insert it into the Nintendo in order to boot up the game. Without the game inserted the power button just blinks and the Nintendo doesn't know what to do. Same thing with your phone. Samsung programs the memory chip somewhere else, then puts the fully prgrammed chip onto the mother board and it boots up. (This is a VERY generic example. There are about 500 things that are different about how these two sysems boot. I am well aware of this. I jus used it as an example to help clarify the concept.)
Skipjacks said:
On your cell phone all that stuff resides on the same internal memory. So if you wipe it clean, it doesn't even have something like a bios that can look for a secondary boot option on an SD Card.[/I]
Click to expand...
Click to collapse
Ugh that seems like a bad design choice. And all manufacturers are doing this? Nobody has managed to squeeze in a separate chip for the recovery, even on tablets?
Skipjacks said:
Samsung probably programs the memory chips on a separate machine before they even put them on the mother board.[/I]
Click to expand...
Click to collapse
So what you are saying is that the process Samsung probably used can't be used after the chip has been placed in the phone without extreme risk? Got it.
Zaron DarkStar said:
Ugh that seems like a bad design choice. And all manufacturers are doing this? Nobody has managed to squeeze in a separate chip for the recovery, even on tablets?
So what you are saying is that the process Samsung probably used can't be used after the chip has been placed in the phone without extreme risk? Got it.
Click to expand...
Click to collapse
You probably need to unsolder the chip from the board and use a chip programmer to write everything back to the chip.
macaumen said:
You probably need to unsolder the chip from the board and use a chip programmer to write everything back to the chip.
Click to expand...
Click to collapse
I don't think I'll be attempting something like that. That would make me even more nervous than wiping the internal memory. I'm a GTAW welder, and I still don't think I would have steady enough hands to go messing with the physical chips inside my phone.
Sent from my SGH-M919 using xda app-developers app
One chip?
Anyway my other question still remains. Android software/hardware is all designed to run off of one internal chip that holds everything? Even on tablets? And nobody has attempted to break this mold?
You can actually adjust the partition details through what is called a pit file (partition information table)
There is a thread where someone was able to create the pit files flashable through Odin. While they are flashable, I have tried everything on my s3 to get it to work. I think there is some bootloader code which ignores unsigned or not genuine pit files. There is just something preventing them from taking effect even though it says it flashed successfully.
You should easily be able to take some blocks from system partition and add them to data without and risks.
Btw it's impossible to hard brick this and the s3. You would just need a jtag device to rewrite the bootloader back to the device. Some people have said that the USB jigs you see on eBay work. And for 5 bucks what the heck lol.
But generally speaking, playing with pit files and partitions can get costly.
Sent from my SGH-M919 using Tapatalk 2
I'm still very interested in this. I intend to only use the Google Play ROM's, which are 500MB, rather than 2GB
Samsung said that the S4's system only uses 1GB more than the S3, yet consumes 2GB more in total :/
DON'T TRY THIS. OTHERWISE IT'LL BRICK YOUR DEVICE
There's a solution for S4 i9500, but apparently it was officially released by samsung. I don't believe samsung or t-mobile will do the same, but I hope so. Or if anything could be done from this to be adapted to m919 would be great.
http://forum.xda-developers.com/showthread.php?t=2429309
Zaron DarkStar said:
Ugh that seems like a bad design choice. And all manufacturers are doing this? Nobody has managed to squeeze in a separate chip for the recovery, even on tablets?
Click to expand...
Click to collapse
I strongly suspect this goes to how ARM Systems-on-a-Chip work. These devices don't expect to encounter any kind of hardware intermediary between the processor and the chips. That's what the drivers are for. These devices are designed for simple bootstrapping, and the best way to do that is to connect the CPU to a single internal store of flash memory. Also, no device manufacturer expects to need to repartition their internal flashes within the device's working life. The partition sizes were chosen very carefully so it isn't necessary. They trade in some leeway space to be able to "set it and forget it." In the end, they don't expect anyone (including themselves) to tinker with it after it's been all set up. Normal users won't be in a position to encounter the recovery system, and even skilled amateurs trying to fix something mildly serious would find the stock recovery system sufficient. If that doesn't work, it's probably going back to the manufacturer.
Still a bad design.
WhosAsking said:
Also, no device manufacturer expects to need to repartition their internal flashes within the device's working life.
Click to expand...
Click to collapse
So when they advertise a device as having a certain amount of storage, yet the actual user controlled usable storage space is almost half that, they don't think people are going to have a problem with that and will want to get that storage space back, through re-partitioning if necessary?
WhosAsking said:
The partition sizes were chosen very carefully so it isn't necessary.
Click to expand...
Click to collapse
The partition sizes weren't chosen by ME, the consumer, owner, and end-user of the device, so it is quite necessary I have control over the storage I paid for.
WhosAsking said:
They trade in some leeway space to be able to "set it and forget it."
Click to expand...
Click to collapse
You mean they trade so of MY hardware's capability for the current/future needs of whatever services they might decide to implement, even if I will never use said services.
WhosAsking said:
In the end, they don't expect anyone (including themselves) to tinker with it after it's been all set up.
Click to expand...
Click to collapse
I tinker with all my electronics to suit my needs. I change the partition structure of my computer occasionally when my storage allocation needs change enough that it becomes necessary.
WhosAsking said:
Normal users won't be in a position to encounter the recovery system, and even skilled amateurs trying to fix something mildly serious would find the stock recovery system sufficient.
Click to expand...
Click to collapse
This isn't about trying to fix a problem. This is about being able to control and use ALL of the storage I expected to have on a device I paid for.
It just sounds like you are making excuses for Samsung. Please don't. It is bad enough that we have to deal with bloatware, but for a manufacturer to reduce a device's functionality, knowing that it is risky/difficult to reverse, for the sake of their proprietary services that the user may not want is just unacceptable.
If I wanted a device where the manufacturer makes the decisions for me the I would buy an Apple. I choose Android for its openness and customizability, so I get annoyed when I see manufacturers deliberately reduce a device's customizability to make way for their proprietary services. I think manufacturers should respect the spirit of the platform they are making devices for, otherwise they are making devices for the wrong platform. More specifically, I think Samsung should respect the spirit of Android, and stop trying to shove their proprietary bloatware down our throats.
Zaron, let me put it another way. The sizes you hear advertised on TV and ads and so on are much like hard drive sizes and the "up to" internet speeds you also see; you're not expected to actually get every last bit that's advertised. The only way you'll fix that is to change advertising laws; good luck trying to get something like that through a legislature.
There's also the fact that those of us here do not represent the typical user of these phones. The average person wants to be able to just get their apps done and be done with it. Quite simply, you can't please everyone, so it's better to annoy a small number of diehard geeks than a larger number of less-technically-literate buyers. As for the "spirit of Android," I don't see any such thing. Android is what manufacturers make of it (like with Amazon). We're talking companies here; not bleeding hearts. For Samsung, Android just happens to be the non-Apple system best at hand. It's not like they're betting the farm on it, either; they're developing Tizen, too, which will be going into their Gear 2 line of smartwatches.
WhosAsking said:
Zaron, let me put it another way.
Click to expand...
Click to collapse
Ok let's break this down since it sounds like once again you are making excuses.
WhosAsking said:
The sizes you hear advertised on TV and ads and so on are much like hard drive sizes and the "up to" internet speeds you also see; you're not expected to actually get every last bit that's advertised.
Click to expand...
Click to collapse
I have gotten nearly ALL of the storage space I paid for on EVERY hard drive I have ever bought. There is a miniscule loss for the formatting overhead and partition table, and maybe a couple hundred megabytes for the Windows recovery partition if I CHOOSE to have one. This is quite minor compared to the 500GB - 3TB of space my drives have. On the GS4, I got nearly half, HALF of the usable storage I thought I was buying. There is a huge difference between minor overhead cost and HALF. Also, most of the time I get exactly the amount of bandwidth I pay for as well, for both my home internet and mobile data. It is rare I get any slowdown. So don't give me this nonsense about not expecting to get what is advertised.
WhosAsking said:
The only way you'll fix that is to change advertising laws; good luck trying to get something like that through a legislature.
Click to expand...
Click to collapse
I don't need to change any laws to vote with my wallet, which is the only thing Samsung should be concerned with: how customers vote with their money.
WhosAsking said:
There's also the fact that those of us here do not represent the typical user of these phones. The average person wants to be able to just get their apps done and be done with it.
Click to expand...
Click to collapse
Really? Because everyone I know who has an Android got one for the ability to customize/tinker with it. But even assuming there is a larger user base I haven't seen that doesn't care as much about customizing, what if said "average people" want to install many apps on their phone? Maybe they want to try out one of the many relatively large Android games on the market. Even an "average" user of a mobile device can do simple math. If they install a few games that are a couple GB each and then run out of space, and then add up the total space they used and compare it to how much their device should have, they would notice they got cheated real quick. All they have to do is go into the app manager in the settings and look at the amount of space used/free to see they don't have as much space as they thought.
WhosAsking said:
Quite simply, you can't please everyone, so it's better to annoy a small number of diehard geeks than a larger number of less-technically-literate buyers.
Click to expand...
Click to collapse
I do agree that it is difficult to please everyone. However, who exactly are they pleasing by cutting the usable storage space in half? Answer: nobody but themselves, in order to exert control over their customers. That is all. I have not heard a single person say, "I am so happy with all of Samsung's built-in services, and I don't mind at all that I have only half the space listed on the box!"
WhosAsking said:
As for the "spirit of Android," I don't see any such thing.
Click to expand...
Click to collapse
When I say spirit of Android, what I mean is the desire to make a useful device that puts the power of customization in the hands of the user. I mean a device that is the opposite of an Apple device. I mean a device that can be used independently of its creator company. I mean the ability to change the ROM, the launcher, the dialer, the SMS app, and allowing pretty much every other part of the device's software to be modular and customizable. I mean the ability to sideload apps, install other market apps, and not be tied down to one marketplace. I mean the ability to have a device that doesn't make you feel beholden to any entity. That is the spirit of Android. So when a company makes an Android device with features that deliberately move away from customization and towards proprietary dependence, aka dedicating almost half of the SGS4's internal storage for proprietary services, while advertising it as having the full 16GB, that pisses me off. If Android was a religion, it would be the equivalent of blasphemy. When I am in the market for a new device, a company gets my attention by having a more powerful device with more customization options. Also, nothing makes me switch manufacturers faster than when I feel like they are trying to lock me in to their economy.
Now, if you respond to me in the same manner as your last two posts, full of industry excuses and reasons why we shouldn't criticize our corporate overlords, then I will assume you are just a shill, and I will ignore you. I have better things to do than argue with a shill, so prove to me you aren't one.
You're right. It sucks. You should get the entire cell phone industry (valued at several hundred billion dollars) to change its' marketing systems.
Let me know how that works out for you.
The rest of us don't like it either, but we've moved on because we learned how to interpret the manufacturer's claims into what we can actually except to see. Now stop yelling at everyone on XDA who is just trying to explain it to you. We're not the ones who came up with these shadey marketing practices. And just because we understand the shadey marketing practices doesn't mean we support them.
You are preaching to the chior. We all agree with you.
Skipjacks said:
You're right. It sucks. You should get the entire cell phone industry (valued at several hundred billion dollars) to change its' marketing systems.
Let me know how that works out for you.
The rest of us don't like it either, but we've moved on because we learned how to interpret the manufacturer's claims into what we can actually except to see. Now stop yelling at everyone on XDA who is just trying to explain it to you. We're not the ones who came up with these shadey marketing practices. And just because we understand the shadey marketing practices doesn't mean we support them.
You are preaching to the chior. We all agree with you.
Click to expand...
Click to collapse
You were helpful to me before, why do you sound so angry now? I wasn't yelling at "everyone". I was disagreeing with one person about the premise that no matter what we do, we should expect to get screwed in some way every time we buy a phone. I don't accept that. I don't even have a problem with people who do accept it, but I do have a problem when people explain it to me, and then sound like they are trying to get me to accept getting screwed. This thread started with me asking if there was a way to easily re-partition the internal memory of the SGS4, and when the answer was basically "no", the purpose of this thread was pretty much served. However, it went on to become a discussion about why things are the way they are, which inevitably led to the business practices of Samsung, at which point it started to feel like I was being told to just accept the situation, which got me riled up. Big corporations wouldn't be big without their customers, so I intend to stay a customer who cares. I won't give in to apathy or complacency, and I won't accept corporate control, even if I can't directly do anything about it. I appreciate the explanations, and I am sorry offended anyone.
Hello,
I have a SM-P600 with Android 4.4.2 (Note 10.1 2014 Edition) and would like to use my 3G USB Key (Huawei E1752) ; This 3G stick works fine on my old TF101.
I've tried to use it with my SM-P600 but infortunetely, it doesn't seem to work, even with the "PPP Widget" apps. PPP Widget displays the famous "No driver found" issue. Josh, "PPP Widget" developer, told me ther eis no way for the moment to make his apps working because there is no loading module (.ko file).
So I wonder if I could use a SM-P601 ROM (SM-P600 with 3G) on my SM-P600 to get the right modules or flashinf P601 ROM on P600 means "brick"?
Otherwise is there another way to make a 3G USB key working on this tablet?
Best regards.
Unfortunately...
Part of the problem is that a custom kernel module would need to be loaded with root, via insmod, and this would need to be coded and constantly reinjected on boot. As far as I know most of these fobs do not make their drivers open-source, specifically, although I could see a possibility in modifying one of the generic drivers from a typical linux full install (likely heavily modified). Even with a ko/kernel module, however, it's possible that the fob might not be able to get enough power from the tablet, itself; I'm not sure what the power draw is, but I have a few laying around; I could probably check that later on.
All of that said, while it may be possible to try to hack something up to work with OTG (for instance I know it CAN be done with external network devices in general (there have been successful drivers built for external Alfa wifi usb-based adapters, but that's wifi), my suspicion is that even if 1) and 2) here were fulfilled, there'd need to be support in other ways built into the ROM itself (I'm wondering if a bunch of the code for this could be pulled from the existent 605 ROM though, which is a consideration). I'm not sure if, for instance, even if JB/KK on the Galaxy Note 2014 were to be made to recognize it, you wouldn't have to disable other things to make it work; I know for the external USB wifi devices, a hack was needed to disable the onboard wifi within the device.
If I had the time or the money I'd certainly be willing to try to make something custom in general. That said, I'm wondering if linuxonandroid (search the forums, or check out linuxonandroid.org) might support it out of the box on the full system img's (given functionality, Kali's kernel probably has the best chance of any of the current available ones, but I don't really know; I'm grabbing the image later on tonight to see what happens if I try)...
In general, though, I suspect that even if this somehow partially works, there are going to be a lot of problems that only a real custom ROM would solve. Though frankly, I can't figure out why nobody has yet. Maybe, like me, people just don't have enough time, and the people who do have time and the skill don't really need a specialized ROM enough.
I'm still kicking myself in the butt for not getting the 3G version for development purposes, personally; hundreds of dollars more for what one could get in a USB fob for 20-30 bucks only sounded like a bad deal til I wanted the functionality; your best bet may be to get a crapper of an android phone for under a hundred dollars and just let it be a hotspot. It's what I finally just gave in to doing. The one upside is decent battery life; if the P600 could supply enough power for the USB 3G dongle to work, all USB-dongled devices, to the best of my knowledge, kill batteries faster than anything built-in would.
Good luck.
Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.
Kasimodo said:
Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.
Click to expand...
Click to collapse
I'd really prefer the same thing, myself. I generally carry around a phone with my other stuff anyway and don't use it for much in the way of voice calls, so it's not too much of a burden. There's also hostapd in linux, or any of a number of mobile routers you can boot up in vbox, if you're carrying a laptop around at the same time; I really hate that our devices, and android in general, won't do 'ad-hoc' networks. I think that's one of my biggest gripes.
I suspect once Ubuntu touch is fully stable it'll be our best option; at a minimum I'm pretty sure I could easily crank out a driver for that. Android, I'm not sure. I'll let you know if I find the time to dig around with with droid though; I've been meaning to learn more about device driver support in Android anyway, now that it's finally pretty much mature.
I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.