Do you guys think that the I9103 is still worth buying? This device caught my attention since it's one of the few that's supported by the "voodoo sound" application and at the same time is equipped with a tegra 2 chipset, but I'm kind of worried about the problems(Lag, unresponsive screen, reboots...) that seem to affect this particular model, were they all solved in the latest roms?
If you don't worry about not having NEON instruction support in the CPU (nowadays almost all devices support it), it's a good device to get. Unfortunately the lack of that support is a very big miss. There are apps that are built with NEON instructions and those don't work on the device. Google abandoned non-NEON devices support in 4.2.2 and few Google apps need tricking to get them working. Otherwise it's a very good device, stock rom is a bit laggy if not debloated, screen is only unresponsive if your fingers are wet and I've never encountered random reboots.
Sent from my OmniROM-powered LG Optimus 4X HD
@Adam77Root Thank you for your detailed reply! It's a real shame about the lack of neon support in the Tegra 2 devices. Could you tell me what kind of apps (Other than the Google now voice recognition and the Gesture keyboard that were mentioned here "https://plus.google.com/+CyanogenMod/posts/8wcuSVkr7zR") might not work on this device?
Related
Hello, im so happy at last samsung galaxy spica have a new home here in XDA
forum. Since i've using this phone i found that samsung galaxy spica only have a
very small number of developer. What a pitty, since this phone have a huge
hardware potential like multi touch capable chip, even some forum found that
spica has a 256mb RAM chip but somehow only about 160mb active.
So im looking forward for developer to help us spica user to unleash true spica power..
theooo said:
Hello, im so happy at last samsung galaxy spica have a new home here in XDA
forum. Since i've using this phone i found that samsung galaxy spica only have a
very small number of developer. What a pitty, since this phone have a huge
hardware potential like multi touch capable chip, even some forum found that
spica has a 256mb RAM chip but somehow only about 160mb active.
So im looking forward for developer to help us spica user to unleash true spica power..
Click to expand...
Click to collapse
not only the hardware i guess, lots of pepole were using samsung spica as it is, since the other android phones were highly priced....so samsung galaxy spica is a well balanced phone between price and ability
What Theoo means by looking forward for a developer to unleash samsung spica true power is not just an empty hope (i guess...)
I recently bought samsung galaxy spica and my first impression is............I DONT NEED ANY SMARTPHONE AGAIN
Hope there will be someone who can deliver samsung spica to its full potential
Infact its a really capable phone.But samsung has written poor divers for it.The 3D experience is horrible.
There are many good developers like leshaK who r working really hard for its development but developing a phone is not a one man's show.
As said above,the phone is capable of multi touch support,it has a 800mhz processor which can be well overclocked like in case of moment,it has a second microphone which seems to be of no use.
If some good developers work on making drivers for this powerful phone,we can use the full hardware capabilities of this phone.
anuragthehellboy said:
Infact its a really capable phone.But samsung has written poor divers for it.The 3D experience is horrible.
There are many good developers like leshaK who r working really hard for its development but developing a phone is not a one man's show.
As said above,the phone is capable of multi touch support,it has a 800mhz processor which can be well overclocked like in case of moment,it has a second microphone which seems to be of no use.
If some good developers work on making drivers for this powerful phone,we can use the full hardware capabilities of this phone.
Click to expand...
Click to collapse
Yeah, like u said, its not one man show. Thats why i hope with our new home here @XDA, someone out there will be interested to develop driver or even roms for our spica. so in the future spica user will have many developer.
theooo said:
What a pitty, since this phone have a huge
hardware potential like multi touch capable chip, even some forum found that
spica has a 256mb RAM chip but somehow only about 160mb active.
Click to expand...
Click to collapse
Could you please post the source/more info?
Is it Rooted?
G1BRICKED said:
Is it Rooted?
Click to expand...
Click to collapse
It is Rooted
MoxFulda said:
Could you please post the source/more info?
Click to expand...
Click to collapse
1. The Galaxy Spica has 256 MB RAM and 512 MB ROM. But only 146 was made visible to the OS.
2.It has a FM capable chip BCM4325, but was not implemented.
3.QT5480 chip is multitouch capable but was not implemented .(hopefully will work in android 2.x ROM)
U can look here for more information
bit.ly/bLcBcP
Click to expand...
Click to collapse
Yes spica has the ability to update to 2.2.but samsung never update their old phone. I7500 for example. It's stop in 1.6.(official fw) .and samsung don't update spica. We have some good developers in samdroid. And leshak give us a 2.2.but not perfect . I hope xda developer can help us build a working 2.2. Our cpu s3c6410 support 3d but no drive. What a pity!
Sent from my GT-I5700 using Tapatalk
Thankfully tom3q working on a brand new 3D driver, but he might be happy for a little a help.
Since he is writing the driver for froyo, I think now our first step must be a stable & working froyo on the spica!
If some developer would like to help in that, the actual state of development can be seen here: forum.samdroid.net/f9/dev-android-2-2-froyo-samsung-i5700-alpha-2-gprs-3g-wifi-11-07-2010-a-1408
P.S.
I would like to say thank you to the XDA Developer team for making the Spica forum!
Adding myself to the bunch of people looking forward to spica development...
Didn't expect to see Spica around here. I'm glad it's here now though, might catch the attention of developers. I agree with some of the people who have mentioned the Spica being crippled by Samsung's poor implementation and support for this device.
I bought the phone in May, and love it for the things that it can do. I just feel that it's too early for Samsung to drop it and move on to their newer phones. This phone has a lot of potential.
Props to Leshak for working hard to improve the Spica. I hope more devs can pitch in.
Hello all, I was hoping for some help in deciding on an alternative replacement from Verizon Wireless.
I am on my 4th LG Revolution and it's time for an alternative replacement, and these are my choices.
LG Lucid 2 http://www.phonescoop.com/phones/phone.php?p=4077
LG Specturm 2 http://www.phonescoop.com/phones/phone.php?p=3726
Motorol RAZR HD http://www.phonescoop.com/phones/phone.php?p=3855
Short Version - Does anyone have experience they would like to share with these phones in the following categories? As it goes, I am leaning towards the RZAR, since I feel that it is a major player.
Call quality.
battery time.
Rooting/Rom-ing?
Media Control headsets
feeling of available support from others on these devices.
Long version.
My needs are podcast consumption, and I read a lot of forums so I have Tapatalk and Forum Runner installed a few times. I use Waze a lot when when I am in the car, and I snap a lot of pictures for writing howto's. Even with a few basic apps installed, the Revolution buckles and lags between app switching and home screens.
I Need my phone rooted for testing corporate VPN, connections. I am a fan of freezing, big-red's bloatware to speed up the phone. I work in IT so know that I have a tenancy to push a device to it's limits.
I did some research and processors in all of them are dual core. The Lucid is 1.2 GHz, while the razr and Spectrum a 1.5 GHz. My thoughts on that are that it will only matter in a year or so, if Ubuntu or FireFox phone OS is still available to play with. I would like to run Cyanogen mod again. (last ran on my OG Droid).
My thoughts are that the Lucid 2 and the Spectrum 2 are mid level phones, so I feel that the LG devices will have much less of a userbase here and on other boards. I am not a fan of the non-removal battery in the RAZR. My wife received that model for her Alternative replacement, she went through three of those before one would finally activate correctly.
I run my podcasts through beyondpod and I love it. I would like to find a phone that would respond to FF/RR controls on a multi button headset. I have had little luck finding info models that have been found to support FF/RW on a headset like the Nexus.
Go with the RAZR HD. Its by far the best on the list. Activation issues are a Verizon problem and/or SIM related so the HD probably wasn't the culprit. The only quality LG phone is the G2 so steer clear.
thesavo said:
Hello all, I was hoping for some help in deciding on an alternative replacement from Verizon Wireless.
I am on my 4th LG Revolution and it's time for an alternative replacement, and these are my choices.
LG Lucid 2 http://www.phonescoop.com/phones/phone.php?p=4077
LG Specturm 2 http://www.phonescoop.com/phones/phone.php?p=3726
Motorol RAZR HD http://www.phonescoop.com/phones/phone.php?p=3855
Short Version - Does anyone have experience they would like to share with these phones in the following categories? As it goes, I am leaning towards the RZAR, since I feel that it is a major player.
Call quality.
battery time.
Rooting/Rom-ing?
Media Control headsets
feeling of available support from others on these devices.
Long version.
My needs are podcast consumption, and I read a lot of forums so I have Tapatalk and Forum Runner installed a few times. I use Waze a lot when when I am in the car, and I snap a lot of pictures for writing howto's. Even with a few basic apps installed, the Revolution buckles and lags between app switching and home screens.
I Need my phone rooted for testing corporate VPN, connections. I am a fan of freezing, big-red's bloatware to speed up the phone. I work in IT so know that I have a tenancy to push a device to it's limits.
I did some research and processors in all of them are dual core. The Lucid is 1.2 GHz, while the razr and Spectrum a 1.5 GHz. My thoughts on that are that it will only matter in a year or so, if Ubuntu or FireFox phone OS is still available to play with. I would like to run Cyanogen mod again. (last ran on my OG Droid).
My thoughts are that the Lucid 2 and the Spectrum 2 are mid level phones, so I feel that the LG devices will have much less of a userbase here and on other boards. I am not a fan of the non-removal battery in the RAZR. My wife received that model for her Alternative replacement, she went through three of those before one would finally activate correctly.
I run my podcasts through beyondpod and I love it. I would like to find a phone that would respond to FF/RR controls on a multi button headset. I have had little luck finding info models that have been found to support FF/RW on a headset like the Nexus.
Click to expand...
Click to collapse
Hey,
One of the reason I purchased a Shield Tablet was the AOSP-like software, which I hoped meant that I would never need Custom ROMS for it. Well, I couldn't anticipate Nvidia's poor firmwares performances : my tablet is slow and unresponsive considering its specs.
So, I'm considering flashing CM11 on it but that would mean I'll loose Nvidia's apps.
What are your suggestions to replace them ? Limelight, Sketchbook Pro ? Perhaps some Xposed Framework add-ons for Stylus functions ?
If suggestions are many, I'll put them all in a chart.
Thanks !
DannyBiker said:
Hey,
One of the reason I purchased a Shield Tablet was the AOSP-like software, which I hoped meant that I would never need Custom ROMS for it. Well, I couldn't anticipate Nvidia's poor firmwares performances : my tablet is slow and unresponsive considering its specs.
So, I'm considering flashing CM11 on it but that would mean I'll loose Nvidia's apps.
What are your suggestions to replace them ? Limelight, Sketchbook Pro ? Perhaps some Xposed Framework add-ons for Stylus functions ?
If suggestions are many, I'll put them all in a chart.
Thanks !
Click to expand...
Click to collapse
I'm 90% certain anything else you flash is going to have the same issues, if not more, since every project out there is using an NVidia device tree and kernel with next to no modifications. Nvidia seems to have really screwed up the graphics drivers in this device - Garmin Viago causes an EGL crash, and I'm guessing that most of the lag/stutter issues are due to graphics subsystem sync issues. (All the specs in the world won't fix a deep-down sync bug.)
I am interested in knowing how many people bother with a ROM that lacks controller support.
For me, its the first thing I found out about a rom. Unfortunately, many developers don't see the need to post controller support in the main sections. I have to scroll through pages sometimes to find the answer.
Controller support is number one for me on this tablet. Gaming is the reason I chose this tablet over any other tablet. It makes very little sense to even bother with any roms that don't have it. IMO.
And some people purchase it because of the specs/price. Stock works just fine if you want to keep stock functionality, or just use the cm builds that have controller support. Also probably a better post for the Q/A section, not development.
By controller support I assume you mean Shield controller? Hooking up a PS3/PS4 controller is easier than changing diapers if you got root.
Well I've tried blisspop for a while, it kinda has support for the controller but from all the roms i've tried including CM, it's probably best to stick to stock with xposed and if you got the space, use multirom to dual boot the device. Custom roms just don't have the support for all the features the shield has, no game streaming, limited stylus support, limited shield controller support and the remote audio doesn't work at all. Basically if gaming is your primary use, use the stock rom.
2kool2Bcruel said:
I am interested in knowing how many people bother with a ROM that lacks controller support.
For me, its the first thing I found out about a rom. Unfortunately, many developers don't see the need to post controller support in the main sections. I have to scroll through pages sometimes to find the answer.
Controller support is number one for me on this tablet. Gaming is the reason I chose this tablet over any other tablet. It makes very little sense to even bother with any roms that don't have it. IMO.
Click to expand...
Click to collapse
I actually don't use this tablet for gaming, I just wanted a powerful, mostly stock Android tablet with an SD slot and unlocked bootloader for aosp/custom roms. I have tried a few other 7-8 inch tablets to replace this one but I ended up sticking with it (stock rom had some multitask lag / can't multitask for beans and custom roms are unstable-haven't tried zombipop tho).
I don't care if a rom lacks nvidia controller support.
Keithn said:
And some people purchase it because of the specs/price. Stock works just fine if you want to keep stock functionality, or just use the cm builds that have controller support.
Click to expand...
Click to collapse
^ This. I bought this device for general use, and to have something future-proof for a few years (unlike my last tablet that was stuck on 4.2 Jellybean). Never intended for the Nvidia controller.
As for the poll, I cannot really vote, since I am on a custom ROM that I didn't download (rather, rolled my own). I tried a build with the controller stuff in the vendor info, that just made the controller app crash over and over. I had to reboot, task kill the Controller app, then use TiBu to uninstall it. Whenever I get around to another build I will avoid the unofficial vendor stuff.
Since it was mentioned here, I may try Bliss in a little while as well.
Hello everyone,
This is a work in progress thread meant to gather info about how to add hotword detection support while the screen is off and the processor is in deep sleep. Ideally, this will work just like the Pixel devices by Google, so you'll be able to get to the assistant by saying "Ok Google" without turning on your device.
Let's start off with the first big question: Is the hardware that's required to do this in our devices?
Well, not every device. I have only looked into Qualcomm SoCs, but this is also possible with some Exynos processors through S Voice.
Qualcomm first added support for Hotword detection with the Snapdragon 800. The only device prior to that processor that had support for Hotwords was the first gen Moto X, which had its own Custom chip separate from the processor. However, my research indicates that all devices after the Snapdragon 800's launch use the processor's DSP for this job.
You can view the announcement of this feature for the Snapdragon 800 at this link:
https://www.qualcomm.com/news/onq/2...akes-mobile-world-snapdragon-voice-activation
In the blog post, the feature is mentioned as Qualcomm Voice Activation. I also found out that this was eventually also backported to the Snapdragon 600. However, looking elsewhere online reveals that this has other names as well, as it is part of Qualcomm Fluent PRO and All-Ways Aware. There are marketing videos for both online, and they all work with the Hey Snapdragon hotword. However, it seems that all of these features are part of the Hexagon DSP on the actual SoC and that they are compatible with v5 and up. So that means that technically all processors in the 600, 700 (in the future) and 800 line should be able to do this.
As far as I'm aware, the only device that uses the Hey Snapdragon wakeup command is the OnePlus One, which has a Snapdragon 801. On its default firmware, CyanogenMod 11S, you could go into the device's settings and train the device by saying Hey Snapdragon three times. Then, you could select the activity that would run every time you said it.
Someone on XDA updated this feature for newer firmware versions and looking at the flashable zip files it has one application file, a modified mediaserver, a modified audio library for its processor and some lib files for voice detection. I haven't attempted to Port this feature for any other device, but I doubt that it would work, even on devices with the same SoC.
I have also looked at Qualcomm's forums and found this thread which has a reply with links that could probably help us out here:
https://developer.qualcomm.com/foru...timedia-optimization-hexagon-sdk/speech/28153
This is source code from the Google Pixel and AOSP which might be the solution to making this work. I am not familiar with C and AOSP's code, so if someone with more experience could check this out, that would be great!
Lastly, I want to mention that I have a couple of devices that could help with testing including my daily driver Xiaomi Mi 5 (Snapdragon 820), a now retired LG G2 (Snapdragon 800) and a Galaxy S7 Exynos which should be able to use S Voice for this but I have not tested it yet. My friend @David_#27 also has a Redmi Note 4X (Snapdragon 625) and I could probably also borrow a Redmi 4X (Snapdragon 435) if we ever need it for testing.
Hopefully we can get some more info on this topic from people that have looked into this more than I have. Please reply to this topic with any info you may have, any help is very much appreciated! Making this work eventually on our devices would be incredible!
Thank you
Bump!
@chrismin13, think this thread is dead...
No one is taking our consideration for real!?
In my opinion it is kind of creepy having the device listen to every sound around it at all times. Many, MANY, exploits were released in 2016 and 2017 specifically based around bugs in mediaserver, and audioserver.
You said this might entail using "...a modified mediaserver, a modified audio library for its processor and some lib files for voice detection..."
So I don't know if I'd even want to mess around with that until maybe even 8.1
Delgoth said:
In my opinion it is kind of creepy having the device listen to every sound around it at all times. Many, MANY, exploits were released in 2016 and 2017 specifically based around bugs in mediaserver, and audioserver.
You said this might entail using "...a modified mediaserver, a modified audio library for its processor and some lib files for voice detection..."
So I don't know if I'd even want to mess around with that until maybe even 8.1
Click to expand...
Click to collapse
True, there are significant security concerns. However, many other devices have also invaded our personal lives, with smart speakers especially becoming more popular lately. I agree, this is scary, but if I'm the one making the code for my device, then I'm more confident knowing what my device does. Also, this is more of an experiment rather than a long term solution. So it's up to you whether you want it or not. I'm willing to take the risk.