Hi guys,
I have bought the phonebaby6s from amazon:
https://www.amazon.com/Sudroid-SOYES-Smartphone-Android-Mtk6572/dp/B01M8LM868/
This phone is terrific. It fits easily in the palm of your hand, runs android 5.1 and does most of what I want from a mobile phone. I'm having some problems with the phone and would like to ask questions about it here. Unfortunately there doesn't seem to be a forum for this phone on XDA developers. The phone seems to be sold by several vendors ( sudroid, Soyes, hippipoo and possibly others. ). I am not able to find a support site. None of the vendors have web sites and there is no information available from google. There are at least two versions of the phone . Mine is LTE but some are 3G only.
On kickstarter right now is a project for the Jelly phone. The Jelly is both larger and has a smaller battery than the phonebaby6s. The PhoneBaby is a terrific device and needs it's own forum.
I want to find info on rooting the phone. The phone is hanging on updates at the moment. I also have not been able to use USB transfer due to unknown device error.
yahoodimenuin said:
Hi guys,
I have bought the phonebaby6s from amazon:
https://www.amazon.com/Sudroid-SOYES-Smartphone-Android-Mtk6572/dp/B01M8LM868/
This phone is terrific. It fits easily in the palm of your hand, runs android 5.1 and does most of what I want from a mobile phone. I'm having some problems with the phone and would like to ask questions about it here. Unfortunately there doesn't seem to be a forum for this phone on XDA developers. The phone seems to be sold by several vendors ( sudroid, Soyes, hippipoo and possibly others. ). I am not able to find a support site. None of the vendors have web sites and there is no information available from google. There are at least two versions of the phone . Mine is LTE but some are 3G only.
On kickstarter right now is a project for the Jelly phone. The Jelly is both larger and has a smaller battery than the phonebaby6s. The PhoneBaby is a terrific device and needs it's own forum.
I want to find info on rooting the phone. The phone is hanging on updates at the moment. I also have not been able to use USB transfer due to unknown device error.
Click to expand...
Click to collapse
Your phone is not an actual supported device made by a real company/manufacturer. Your device is one of the devices known as a "clone". There are a lot of so-called "companies" that use various pieces of cheap Chinese hardware components that were originally designed for other devices, they put all these components together even though they weren't designed to work with each other(similar to building a car from parts of other cars) then they "hack" together an operating system for the device, usually the OS on a clone is unstable.
They do not have an actual company to support the device, they have no stock source code to release and no stock firmware to make available to the public. This is because the devices they make are not all made of the same combination of components and this makes it impossible for them to have a stock source code or stock firmware because each of the devices would not be able to use it even though the devices all "look" the same and have the same "name".
You probably won't find any kind of information about the device and I can almost guarantee that the device will not be supported at XDA unless you do it yourself. There are no developers that would ever own or work on that device because it's not something that any of them would be interested in, they all have much better devices than that and they only work on the devices they personally own. If you want root and custom recoveries or ROMs then you'll have to figure all that out and put it all together for yourself. And even if you do all of that and build your own recovery and your own ROMs and post them on XDA, it still won't get its own forum because I can guarantee that there are not enough people that own that device, XDA only creates forums for devices that have a large community of users that own the device.
Your device is just too "unknown"
Get a better device and stop buying generic Chinese devices.
Sent from my SM-S903VL using Tapatalk
Related
Hey people,
I just want to say something that is bugging me about android updates. It is depended on what manufacturer you have for getting system updates(eclair, froyo...) and most of them don't release updates for some reason about google or their own policies(for selling new devices, maybe incompatible(!) or else). But we see some groups release custom roms for popular models. that means they are compatible and it can be done. and some devices don't get any or get not fully functional roms because of their developers are not so talented, they have small developer group or other reasons. So this device owners never gets new apps or functionalities they may have. So my question is will we have to toss that devices to trash or is it possible to make system updates device independent?
Thanks.
It is not possible to make a universal update, because all devices have their own specific hardware builds that need to be compensated with specific drivers to make use of what that Device can do. Even custom roms only work with one device or another similar product. Also every company wants to make their software unique to the rest of the crowd such as motorolas motoblur and samsungs touchwiz. So no, there never will be one update that works for all because of hardware.
First off let me say that if there is a better place to ask this please let me know!
I want to create a portable android device and I am having a little bit of a hard time understanding what I am looking for/need.
What I am trying to do is create a "wearable phone" per-say. Think of the "Fallout" game's PIP BOY... but for android... and be a phone too (really important for it be a phone).
The ideal thing I'm looking for is a android compatible board that has the ability to be flashed (CDMA) for phone service (Ideally Verizon/Cricket). I would like to not buy a phone and tear it apart and use it... I would have already done that if that's what I wanted to do.
I have seen things like Allgo boards and I have also seen things like BeagleBoard that is android compatible and it has a lot of nice ports like ethernet and usb.
I would like options like bluetooth, wifi, cmda, audio out, low power consumption. Kinda basic things for a phone. It also has to be relatively small.
Some things that would be nice but not needed are options like video out, high capacity storage options (usb flash, sdhc card, or solid state), etc. I would possibly look into dual booting into Linux or Windows CE but thats not nowhere near important right now.
As I said if there is a better place to ask this please let me know! Thank you for your time.
it's hard to find one part at a time. it's also more expensive. it's going to get harder when you build your android OS.
you need to have a team. a big one.
The BeagleBoard and AllGo boards already have android support and kits so that shouldnt be too hard to put together for the android side of things.
I figured the phone would be the hardest part. Is there a way to put the phone part into something like a android device/"mini tablet"?
good. you found the hardware. but as i said: find a team.
you need the hardware to interact with the software (and software to interact with the hardware) more like building an app in android SDK. by that you need a programmer, with experience of building a mobile OS (MIUI is based on android 2.3, they made it from scratch). then make a screen size and a chassis, which is hard because you want it like a large digital watch.
find help in this forum. there are alot of devs you know
Phone + strap + superglue = winning??
Sent From My Fingers To Your Face.....
hiu115 thank you for your input. what i would really like to know is if there are resources to make it... team or not. I CAN get a team and CAN program if i need to. I am just at a loss for the phone hardware. The android part (hardware/software) is "easy"... the phone additive is illuding. I need a prototype for proof of concept. A lot of my work is done for me it seems.
if i get nothing else out of this thread I would like to know if it is possible to add (for that matter find and buy as well) hardware for the phone part. I would like CDMA. At least tell me if you know what the part name I am looking for is... and where to find it if possible too.
conantroutman you dont get a thanks... funny though... but not helpful ... that IS kinda the point though. (EDIT meh you get a thanks too i guess)
Will be watching this, I once was thinking about doing it, would be awesome, also if you can get hardware to a similar device which is out it would be easier on the sift ware side
Sent from my GT-I9100 using XDA App
Here are some examples:
linuxfordevices.com/c/a/News/LiquidWare-DIY-Android-Modular-Gadget-Platform/
technexion.com/index.php/arm/ti-omap3530/inferno
(just put www in front)
Cheers I will just look
Sent from my GT-I9100 using XDA App
Ah ha!!! I think I found a better way to ask and get the answer I'm looking for!
What makes a Android device a phone? (Don't say "that fact that it can make calls" I'm looking for the name of the part)
Is there a way to turn an Android device say either custom built or purchased tablet into a phone with like a 3g modem or similar. If so what is that thing I'm looking for!?!?!
I'm not sure if this is of anyhelp, but details of a Qualcom GSM/CDMA chipset
http://www.mobileburn.com/news.jsp?Id=145
Ok... if you want to build a custom android device, the first thing you need is a template... Start with a development board.
The beagleboard is a great board to work with, however it's large and you won't be able to use it other then a tablet on its own....
The KIT-S5PC110 deb board is a good one
People recommend PandaBoard over BeagleBoard as they are basically the same specs but the PandaBoard is dual core.
Here's a link to ARM Dev boards http://www.armdesigner.com/products.html
I do believe that if I were to select a kit for development currently, based on what I've seen out there, I'd go with a originboard. http://www.origenboard.org/
Now, the other thing you will need is to learn some asian language Here in the USA, we are falling behind on mobile technology. You will find more Asian language forums then you will english
Once you have played with the OS a bit, and figured out the specs, you will have a custom circuit board made. Basically for board manufacture, you will simply eliminate all the features you do not want on the dev board to make it smaller. Then you make the board with the remaining hardware. You can probly talk to the Origen guys to get one made. They make their hardware as open as possible, so they will give the specs to the manufacturer of your choosing. This is where it gets costly.
After the board is created, you will build a custom housing for your box. You can prototype these housings on a 3d printer like RepRap or MakerBot... This requires precise CAD drawings. Or you can source it out to someone else.
Finally, build a box and slap a price tag on it.
It's usually a large effort to build a custom android device... However, check this article out from Hackaday.com today: http://hackaday.com/2011/10/10/how-to-build-a-23-android-tablet/
There have been a few fallout builds on hackaday in the past (I'm a daily reader).. http://hackaday.com/2011/09/06/fallout-brought-to-life-with-this-working-pip-boy-3000/
MacaronyMax: thanks that was informative i didnt knwo they could do that
AdamOutler: You seem to know what you are talking about. I do know some Japanese btw but what I really wanted to gain is can a phone module be added to call people from it. I would like to do this without needing internet like wifi connection. I would like to flash it and use a phone number to call people and recieve calls. CDMA would be preffered.
Most of the manufacturers keep cellular technologies locked down. That's the single bit of power they maintain. The rest of the board can be open source, but they lock down the cellular technologies.....
With that said, you can get a "CDMA Cellular Module" for just about any purpose and communicate with it via GPIO(power), UART(Data) and I2C(controls). That would be one way of going about it....
An easier method might be to grab a Samsung Captivate from Ebay, remove the housing and build around what's left. I say Captivate because they are around $200, decently fast, and they are rather slim.... Also, they can be modified to be UnBrickable and we've done alot of research and custom roms in the Captivate Development Forums... an i9000 may be even better, but it's got a larger case... Captivate and i9000 are basically the same phone and some of the most active development forums on the site.
Using a prebuilt device and remanufacturing the case would suit your requirements and possibly be easier I think.
Ok so what I have found are these things called "PCIe minicards" that can do cmda/gsm/gps/wifi and all that good stuff. Is this what your talking about?
If I found a board, that has the slot for it, will this be able to be used for voice calling over say Verizon/Cricket if I added it to my plan? If so would this be flashable with qpst/cdma ws or what would I use to program?
I also noticed some boards having what appears to be the same device (usualy wifi/gps ony) but it looks soldered on. Might replacing one of those for one with cdma capabilities work? (I think i saw this on a new pandaboard)
The reasons I dont want to use a pre-exiisting phone is because 1) I dont get to learn anything 2) I can't "upgrade" anything and 3)I don't want limitations set by manufacturer (ie. phone needing root, etc)... plus I kinda like the from-scratch look of things.
Can anyone answer me these 2 questions? They're just eating away at me right now and its making me so confus.
1) Why does each Android device need to be individually updated to the latest OS? I mean they say its because the hardware is different on each device but look @ desktops and laptops, there are so many variable hardware parts yet every time Windows updates the old hardware is compatible with the new OS and updating is a breeze. Why is this so different for Android?
2) Why do manufacturers feel the need to lock phones down so much? For example, the only thing holding us back from having a functioning ICS ROM is the RIL, which Sammy refuses to release. Carriers and manufacturers alike get so much hate for always lagging on updating our phones to the latest OS, but if our phones werent so locked down they would never have to worry about updating a phone again because the dev community would take care of all of that for us. And if they decide that one of the 3rd party dev releases should be released OTA instead of forcing us to go online and do it ourselves then they could contact the developer and compensate them for their work so they could get permission to release it. They save time and the devs get money for something they normally do for free. Win win from my perspective.
It comes down to drivers. Computers are a mix of parts that weren't necessary built to work together in the exact combination, so all of the manufacturers provide drivers to make their parts talk to the OS in a common language. Android phones have this too, but the drivers aren't generally available to us a users; they're only provided to the manufacturers, or written specifically by the OEM, and may be under various types of NDAs or close sources licenses. Android as an OS isn't written for a specific phone or device combination (save for the Nexus releases) and does not include the drivers, so it's up to the OEM to compile it with all the drivers needed to run on a particular piece of hardware. Without those drivers, the OS won't work with a particular device.
As for the RIL, it's my assumption that it's under a closed source license provided to the OEM. Samsung has been pretty open about things, so it's more likely it's Qualcomm/VIA that has the controls in place and completely out of Samsung's hands.
Shrike is dead-on with drivers. Lockdown is also a support issue. Support a couple hundred desktops where every tom **** and harry can do whatever they want? Service packs, patch Tuesdays. fun fun fun. lock it down and only deal with apk's that don't work or don't play well together. manageable chaos is the goal.
As posted in the Title, I need a tablet to use for dev/test/demo purposes. Mostly B2B applications. I'm having a hard time finding one that meets my needs. Please help!
Preferences:
1. Would like to stay as close to stock android as possible.
2. Updates and Support. There are two routes in mind, a very cheap device that we would have to replace frequently, or preferably a more solid device that will get updates for years to come.
Side note: Root and custom rom might get approved with a device with a factory unlock-able bootloader. This would have to be from a company with a good track record like OnePlus for example.
In the past we've used Nexus devices for dev/test/demo purposes. Now that those are no longer made, we'll probably get a pixel 3a for a phone form factor. They've supported the original for over 3 years now. Correct me if that's not a good option.
Mods, feel free to move this if there is a better place for this question.
Hi All,
While I was searching for a new device to purchase, this question popped into my head: how do ROM developers decide which devices to support? Admittedly, this question arose because I wanted to find a phone that would be compatible with the most ROMs and is currently still under active development. But I also am genuinely curious as well.
I'm new to the custom ROM scene and just started researching but from what I can understand, most, if not all, developers are doing this on their own free time without any sort of payment. In that case, I would assume, they would only support devices that they have access to, in other words, devices that are currently using and have used. Additionally, developers are probably tech-savvy so I am also assuming that most developers will choose a phone that they think is best. Although what is best is subjective, I believe that there are a common set of desired features which will lead to a couple of devices being more popular than others. As a result, some phones will see support from a wide variety of ROMs while others will see a few or none at all.
I went through a couple of the ROMs I was interested in from this list (https://www.xda-developers.com/the-most-popular-custom-roms-on-xda/), and found that Nexus 5x was common between them all. I can't recall what phone was popular during 2015 but was this phone really so popular/desired that all ROM developers seems to have one lying around in 2019/2020? Its been past 4 years since its launch and I assume that its specs are very outdated compared to what we have now but it is still being supported by many ROMs. What lead to this phone to become such a commonly supported phone by ROM developers?
The Nexus line was at a good price point, good hardware for the time and fully supported factory images from Google with regular updates, next to impossible to hard brick, worked across multiple carriers worldwide, easy to unlock bootloader, custom recoveries available, and popular following. I'm sure I've missed something [emoji846]
Device's that are only available in a limited market, or are unable to be bootloader unlocked, don't have factory images are difficult to support and have a limited following reduces the likelihood that a person interested in developing will buy that phone.
ktmom said:
The Nexus line was at a good price point, good hardware for the time and fully supported factory images from Google with regular updates, next to impossible to hard brick, worked across multiple carriers worldwide, easy to unlock bootloader, custom recoveries available, and popular following. I'm sure I've missed something [emoji846]
Device's that are only available in a limited market, or are unable to be bootloader unlocked, don't have factory images are difficult to support and have a limited following reduces the likelihood that a person interested in developing will buy that phone.
Click to expand...
Click to collapse
If you don't mind, could I have your opinion on Moto G5 Plus in regards to ROM support? It appears to be supported by Pixel Experience, AOSP Extended, and ResurrectionRemix so it looks like it has a fair amount of support. However, when I view the top devices page on XDA (https://forum.xda-developers.com/top) I don't see the Moto G5 Plus. Would there be any relationship between the top devices on XDA and devices supported by the most ROMs?
No, there really is not a correlation between the top devices on XDA and ROM support.
The top devices reflects basically the activity within the forum. So new device releases will trigger people's curiosity so even though there may be zero ROM support, the device has activity.
A device like the Moto G5 plus that has been out for awhile, just doesn't have loads of activity in the forums. There is still activity on ROM threads, but it's more sporadic.
Got it, thanks for your help. Looks like I'll just have to keep digging through the forums and rom websites and try to make an educated guess about what device has and will continue having the most rom support.
The lineageOS support for the Nexus 6 is ongoing and that phone was released in 2014. There was a lot of passion surrounding that device, but as developers had their device fail (battery died, screen broken, ect), they moved onto other devices.
My point is, the best you can do is find a popular phone in your price range and hope. The OnePlus series may be worth looking at.