Related
My question is for overall but I'm going to stick with one main example:
One thing that no Android port for Raphael has is camera support. Many HTC devices, WinMo and Android alike, have the same camera specifications, 3.2 megapixel with auto focus. It seems economical and logical to me that HTC would use the same exact camera make/model on multiple phones since by design they are going to share the same camera specifications anyway. In that case, shouldn't it be possible to use the Dream's camera driver?
Apparently my assumptions are wrong somewhere since we still have no camera support, so what exactly is going on?
Thanks!
.
the problem is there is no android drivers for the camera or the devs havn't sorted the the kernel yet,
like for the first couple months there was so bluetooth but now there is it will all come as long as interest is still here
I don't think that was palmboy's point.
I think that although they're the same resolution, if the camera models between the two phones are different and the wrong drivers are used, too much power could be sent to the camera and it could break it.
I guess the best way to make drivers for the camera would probably be either to edit those for a phone with similar specs like the Dream according to the WM drivers of the Raphael camera, or to just start from scratch. It would be very risky to just use the Dream drivers on the Raphael.
Actually, AFAIK, the Raphael and the G1 had the EXACT same hardware. So in normal logics you'd think it's an easy port.
But it just isn't because we have no doc over the drivers nor nothing.
But I can't really explain all this, I'm not a developer
Oh right, I thought they would be (at least slightly) different. Now I'm a little confused
Hello,
This phone looks really interesting, but I don't think Samsung will care about it after the promised 2.2 update. Furthermore its predecessor, the Galaxy, suffered from both a total lack of custom roms.
So my question is do you think there will be good custom roms for this phone for newer android versions ? Is it possible (eventual problems with drivers, etc..) ?
Thanks for your answers
Paul O'Brien @ MoDaCo has just tweeted that he has rooted his own Samsung Galaxy S, so im sure that he will produce some great things for this phone as he has done with many other android phones. I hope its soon
I'm pretty sure there will be some awesome custom ROM s. This phone will be on the top 4 US carriers and US cellular. There will be a lot of new developers coming to this forum once the device is released.
DAKIDD236 said:
This phone will be on the top 4 US carriers and US cellular.
Click to expand...
Click to collapse
I consider this more of an annoyance since there will be like 5 different rom types (4 US versions plus the Europe/Global version) because so far every version has a different hardware configuration. AT&T and T-Mobile versions have different buttons (4 instead of 3) and no front camera. The Sprint version is a totally different phone with camera flash, a keyboard, and unfortunately, only 1 GB of storage (Link). The Sprint version also has no front camera and comes with 4 buttons. No details on the Verizon version. It's inevitable that someone will flash with the wrong rom.
The Captivate for AT&T has almost identical hardware to the I9000, as well as having a front facing camera. the only thing that was rly changed on this phone from the I9000 was the body design and the extra button.
sunshine1982 said:
The Captivate for AT&T has almost identical hardware to the I9000, as well as having a front facing camera. the only thing that was rly changed on this phone from the I9000 was the body design and the extra button.
Click to expand...
Click to collapse
Hmm...i actually read that it won't have the front facing camera.
clubtech said:
Hmm...i actually read that it won't have the front facing camera.
Click to expand...
Click to collapse
Captivate will have front facing camera and Vibrant on t-mobile does not have it. Vibrant actually looks identical to the Galaxy S, but Catptivate looks totally different(i think it looks better). Captivate looks=SE X10 looks, Galaxy S/Vibrant looks=iPhone looks??
edit. both of those links are telling that they both have secondary camera, but pictures of the phones are without front cameras.
here's the Samsung Captivate and Samsung Galaxy S I9000 compared on gsmarena
http://www.gsmarena.com/compare.php3?idPhone1=3408&idPhone2=3115
Remember Samsung holds a tight lock around it's drivers. So don't expect anything to awesome with these roms. No wifi tether is obvious and all roms will be based on Samsungs current 2.1 release. It's impossible to port anything from HTC or Motorola onto a Samsung phone because of the crazy partitions and security they have on it.
Yeah that was the problem I was referring to when creating custom firmware..
I'll buy another phone I guess
I'm not an expert, but don't think that's true. As SGS is rooted and Paul is currently preparing the kitchen @Modaco it looks like the bootloader is not locked like motorola milestone. Thus there's no problem to have custom roms, or?. Froyo is secured (according to samsung) so drivers will not be a problem in near future imho.
P.S. as I see some other phones with the same/similar hardware are announced to come in the next several months so pretty much there will be drivers available..from one or another place. But this is valid concern for any android as a matter of fact...except nexus 1, which is out of my scope due to the bad HW
P.S.S Another .02c - if the functionality promised is working as charm and the remaining phone's issues are solved in the near future...is it so important to have the latest gimmick that re-starts the troubleshooting from scratch?
P.S.S.S Samsung is a better choice than HTC... Many reasons.
dlci said:
I'm not an expert, but don't think that's true. As SGS is rooted and Paul is currently preparing the kitchen @Modaco it looks like the bootloader is not locked like motorola milestone. Thus there's no problem to have custom roms, or?. Froyo is secured (according to samsung) so drivers will not be a problem in near future imho.
P.S. as I see some other phones with the same/similar hardware are announced to come in the next several months so pretty much there will be drivers available..from one or another place. But this is valid concern for any android as a matter of fact...except nexus 1, which is out of my scope due to the bad HW
P.S.S Another .02c - if the functionality promised is working as charm and the remaining phone's issues are solved in the near future...is it so important to have the latest gimmick that re-starts the troubleshooting from scratch?
P.S.S.S Samsung is a better choice than HTC... Many reasons.
Click to expand...
Click to collapse
Samsung's drivers are proprietary and encrypted. You still have to wait for them to be released in order to get anything to work on a Samsung device or else the device will have no display/sound/antenna's. The bootloader was hacked on the Behold 2 but we still had no option to flash from the phone. That means ODIN is the only way. Behold 2 was rooted and still had no wifi-tether and no choice in custom roms (it was whatever samsung released + optimizations). HTC has Samsung beat with hackability.
Ok, I understand now what you mean. Didn't know that.
Too bad with this encyption story...
edit:we wouldn't have gingerbread if samsung won't release it,is that right? No chance to get something "new" if samsung doesn't release it directly?
°Dexter° said:
Too bad with this encyption story...
edit:we wouldn't have gingerbread if samsung won't release it,is that right? No chance to get something "new" if samsung doesn't release it directly?
Click to expand...
Click to collapse
If they release it for another Samsung phone then it's possible that it could be ported but not certain. There is a 2.1 rom for the Galaxy. Eugene tried to port it to the Behold 2 and got almost everything working except for the most important thing which is sound. Wifi/BT/data/video were all there but he just couldn't get sound. We had a 1.6 rom well before the official release only because Galaxy had it first (also someone got a secret behold 2 beta a month after the Galaxy rom was released) and it's only problem was it didn't have vibrate. It's just nearly impossible to do anything without something from Samsung.
A good read if you want to understand what you're getting into when you buy a Samsung phone. http://androidforums.com/all-things-root-behold-2/63246-dev-needed-2-1-running-behold-2-a-4.html
mmmm, so, the combination of encrypted drivers and poor samsung support i.e. firmware updates, means that we wont be able to run 2.2 ROMs unless samsung releases 2.2?
and also further android versions are a no go?
already been burned by motorola with milestone and its locked bootloader, dont wanna burn again.... seems like the only option is HTC
psychoace said:
No wifi tether is obvious and all roms will be based on Samsungs current 2.1 release.
Click to expand...
Click to collapse
But there is wifi tethering. I set up a mobile AP on my UK Vodafone SGS to allow a guy in the office to activate his iPhone 4!
psychoace said:
Samsung's drivers are proprietary and encrypted. You still have to wait for them to be released in order to get anything to work on a Samsung device or else the device will have no display/sound/antenna's.
Click to expand...
Click to collapse
Are you sure about that? Recording to this thread the galaxy s source samsung released includes drivers with wlan and camera mentioned as examples:
http://forum.xda-developers.com/showthread.php?t=696863
o shi. if what you guys says here is true and there is no way to make new roms for the samsung or get new android version until samsung make them because of the DRIVERS that's a no go Galaxy for me plus tether is a Must Have for me .... damm u samsung. that was the only phone in t-mobile that I like I guess I'm gonna have to switch from carrier after all
I think we can't really compare GS with Behold 2. GS will have lot more support from Samsung. Also i have faith in Paul's work, he will come with some serious ROM's.
I wouldn't surprise if he would port Froyo to GS before Samsung. He already had fixed stalling issue, now i could feel real hummingbird humming in my GS.
Hello world,
I currently have a galaxy s2, running lollipop. I've stretched out the use of this puppy pretty far, but I've decided it's time to upgrade. At first I figured I'd go with something like an s5, but then I discovered the g3. It looks great, but of course the biggest design difference is the rear buttons. I can tell from reading that g3 owners really love it, but I don't have access to get my hands on one, and I'm hesitant to make the jump.
If I get one, I'll definitely root it, and I may install a custom ROM. Do custom ROMs still support the "knock on" feature? Would it work natively for most ROMs, or would I have to be careful about finding a ROM that supports it? Having that feature definitely makes the rear buttons less daunting. Does the knock-on feature eat up battery life?
I also like using my side volume keys to take pictures instead of the screen; does the rear button help with taking pictures, or is it easier to use the touchscreen?
I've never even used a navbar before, so jumping from all hard buttons to the g3 bezel is a big change for me.
Anything else I should know to help me decide?
Thanks for the advice!
I had a S2(plus) before i got the G3, you will get used to the back buttons pretty quick.
The rear buttons are good for non-landscape photos like selfies.
Some custom roms have the knock on feature, but they are based on the lg stock rom.
Also, you can find the G3 pretty cheap nowadays so if you are looking for great performance and good battery life(on MM) get the G3.
(Also, if you can, try to get the 32gb model as it comes with 3gb of ram)
E: the navbar will feel wierd at first as the back button is on the left side, this can be changed in the settings.
Sent from my Lg-G3
Knock on has worked on every Rom I have tried, and I've tried a bunch. It does not noticeably reduce battery life.
Because there are no side buttons you need to use the screen to take photos, its never been a problem for me and the G3 takes some pretty good pictures if you are on an LG based Rom. Aosp or CM roms have no access to the cameras potential and end up taking pretty bad pictures compared to stock... Passable but stock is just that good.
My best selling points would be that this phone is still getting updates, is rooted, extensive development, performance on par with current flagships (for everyday use, not so much for gaming), has a very high screen to body ratio, has an or blaster, great battery life, SD card, removable battery, and great screen... It's hard to find a better phone and I have been looking.
I upgraded to the G4 when it came out and couldn't deal without root but it might be worth checking out now.
Every other phone either doesn't have root or doesn't have enough to beat the g3... My current work phone is a note 5 and I love/hate it... So much potential but no root and no sd
So it sounds like I would have to be careful about choosing just any ROMs. But are there a good amount of options that are stock-based, with room for customization? I tend to like the feature set of slim-based ROMs.
Thanks for the tip about the 32gb. I'm planning to spend about $200 on swappa, so it's right up my alley.
Thanks again!
arttuh said:
I had a S2(plus) before i got the G3, you will get used to the back buttons pretty quick.
The rear buttons are good for non-landscape photos like selfies.
Some custom roms have the knock on feature, but they are based on the lg stock rom.
Also, you can find the G3 pretty cheap nowadays so if you are looking for great performance and good battery life(on MM) get the G3.
(Also, if you can, try to get the 32gb model as it comes with 3gb of ram)
E: the navbar will feel wierd at first as the back button is on the left side, this can be changed in the settings.
Sent from my Lg-G3
Click to expand...
Click to collapse
jomo86 said:
So it sounds like I would have to be careful about choosing just any ROMs. But are there a good amount of options that are stock-based, with room for customization? I tend to like the feature set of slim-based ROMs.
Thanks for the tip about the 32gb. I'm planning to spend about $200 on swappa, so it's right up my alley.
Thanks again!
Click to expand...
Click to collapse
I've had my G3 for half a year now, loved it.
Regarding your questions,
- Almost every single rom is equipped with knock on feature (double-tap to wake), while knock code (tapping a preset sequence on your screen-off) is only available on stock roms. Yes it's integrated natively, and no it doesn't eat up battery life.
- Yes you can use volume buttons to take pictures on G3, just that they are on the rear now. I actually prefer this because it's more natural to use my index finger on the read to take a picture, as compared to pressing side volume buttons on my old Optimus G. You'll get used to the rear buttons and find that they are much more comfortable to use than side buttons.
- You will probably get used to the navbar really quickly, given that it works the same way as physical buttons
- There are a variety of roms to choose from, and the best stock-based I've used so far is the Ti-X rom which is a continuation of CloudyG3 2.5. Some of them may not be on xda but on Google+ you can find more (NovaStock, Lion rom, etc.)
A few pointers you should note:
- Marshmallow, as of now, is only out for Poland and Korea G3, though it will roll out to other countries soon enough.
- There have been reports of overheating but recent updates solved that issue for me so yay!
- AOSP roms like cyanogenmod, candysix, etc, will not be able to make use of the full potential of the camera. You can flash camera mods like m9 camera mod but it will still not be as good as on stock.
First of all, apologies for the poor english and if these questions were already answered. I already read some of the things i wanted to know so but it was some months ago.. i'm hoping most have changed.
I have a moto g1 since it came out. It had Android 4.3, received update for 4.4, 5.0 and 5.1.. I never had the need for a custom rom.. the stock ones are super stable. Nowadays 1GB of ram is nothing, even for a light user like me.. i literally only have 3 or 4 light apps apart from gapps.. A custom rom will give me more features but won't make my phone (much) faster.
I had my eye on this phone for a while now but there are some things that make me think twice. I have some questions for you.
-Lets start with acessories.. is there any screen protector on the market right now for the Z2 that doesn't peel on the edges of the curved glass? If you have one, can you post a pic so i can see if it stays neat?
-Is the phone receiving official updates? Are they any good? Did those stupid quirks i read about some months ago vanish?
-Is there a way of putting soft navigation buttons on the official rom (i don't care about the gestures on the fingerprint reader)?
-What's the state of the custom roms compared to the official? Not talking about having more features.. are they as stable as the original ones and does everything that works on ZUI, also works in the custom ones?
-For someone that doesn't want a phone with a screen larger than 5" (something smaller would be even greater), do you recommend this phone or have a better alternative at the same price point (~200€)? I highly value the stock android design and above all, something stable. I don't mind a phone with less ram and even lower specs than the Z2 if it meets those things i prefer on a phone..
-Are the community roms making good progress? By this i mean, do you think we can have something near 100% stable in the future or the lack of source code will never allow it?
Many thanks!
It is receiving software updates. I don't know about which "quirks" you are talking about but the updates are okay... Not perfect minor bugs in notification bar etc.
Yes you can enable soft navigation buttons. Its in settings.
You can also go for redmi 4.
But for 11000₹ this phone is a steal deal in my opinion. I bought it for 15k.
PS. I too was a moto g1 owner before this and I also have most of your doubts.
-Lets start with acessories.. is there any screen protector on the market right now for the Z2 that doesn't peel on the edges of the curved glass? If you have one, can you post a pic so i can see if it stays neat?
-> Somehow, i never put glass/screen protector for every curved glass phone i ever had including this one. Well this is personal tho..
-Is the phone receiving official updates? Are they any good? Did those stupid quirks i read about some months ago vanish?
-> Yep. Yep, they're pretty good on developing. Which one?
-Is there a way of putting soft navigation buttons on the official rom (i don't care about the gestures on the fingerprint reader)?
-> Yep, built in
-What's the state of the custom roms compared to the official? Not talking about having more features.. are they as stable as the original ones and does everything that works on ZUI, also works in the custom ones?
-> ZUI wins on Camera, so far. Porting ZUI cam status is on progress
-For someone that doesn't want a phone with a screen larger than 5" (something smaller would be even greater), do you recommend this phone or have a better alternative at the same price point (~200€)? I highly value the stock android design and above all, something stable. I don't mind a phone with less ram and even lower specs than the Z2 if it meets those things i prefer on a phone..
-> Go for it, awesome phone at its price, but dont expect too much on Cam, its 13/5..
-Are the community roms making good progress? By this i mean, do you think we can have something near 100% stable in the future or the lack of source code will never allow it?
-> Yeah, they're fookin awesome developers, lots of ROM goin Official right now.. have a try on RR or DU
Many thanks!
No Worries, cheers!
I appreciate your replies. The phone now is out of stock on gearbest (the only place i can buy so i don't pay customs).. let's see if it comes back since the brand is apparently dead now.
Is there anyway to swap a z2 plays rear camera for the z2 force's rear dual camera? Would it work and if not why not. Thanks
Imagine this: have you ever tried putting a 9v battery in an AAA slot? It's physically impossible unless you modify the structure of whatever device is using them. And if you somehow manage to fit it, the device isn't guaranteed to work with it, and it can even stop working.
Same situation here, if you somehow manage to change the lens, there won't be space to fit them (z2 play is 0.1 mm thinner than the z2 force). If you surpassed all those steps, good luck trying to connect into the motherboard both cameras. If you are a ****ing hardware genius and somehow you managed to fit the connectors into the z2 play's motherboard, then good luck developing drivers for those lenses to work in the SoC of the z2 play (and I don't think the ISP supports two lenses at all).
I don't know what happened through your mind to even think that... That's a pretty dumb question.
Well thanks for the reply and never even thought about the other cam having a different connector not even sure if it does but I suppose it could. I personally don't think it is a stupid question, both phones are Moto's and the same series z2, I do understand they have different motherboards and processors, not so fluent on android but since people on here use custom ROMs thought I'd ask. Guess I should have thought about the drivers issue though. Anyways thanks for your response. I suppose I was hopeful for the play 2 to have a better and dual camera. I use it has my primary, because I can Bluetooth tether without turning off Wi-Fi which I can't do with the z2 force Verizon model, this also worked for me on the e4plus but not on z play Verizon model, I really don't understand why some models work for this and some don't, doesn't make sense to me.