it shortly I have 2 motherboards from models u8800 and u8800-51, the processor's bottom plate and sensors and camera + audio speaker is on the other plate.
I changed the plates where the processor places from u8800 to u8800-51 ...
I must say that everything is working perfectly except bluetooth. not find drivers, because drivers must be those from 8800-pro.
I identify a few small changes in architecture boards but the processor is the same with the same chipset...
combination is stable no bugs or lags ... I've tried so far aurora, cm 7 and miui, where I chose and
I need a patch from wi-fi drivers u8800-pro! please help.
Yes, Bluetooth drivers and rils seem to work together. The only problem is the wifi unfortunately hence the problem from the pro/ 51 issues
Sent from the hands of my Impulse 4g.
Related
Even if blade can run ics,also imply all new functions can be work on blade?Such as live video effects , face detection ,panorama mode.....I was worry about these new functions can able to run on blade.I think the blade's camera is so weak.
I think the developers are still having trouble making the camera work at all, it could be a while before it's a fully functional rom. There are still some bugs with the way that cm7 handles the blade camera, which reduce the quality.
Those functions you listed should all work, once they fix the camera, within the hardware limitations of course. I've no idea how long it'll take, maybe 1 or 2 months.
Face unlock isn't going to work because of no front facing camera, but most other features should work fine, once they've been fixed.
What about hardware acceleration? Is Blade capable of it?
Yes it should be.
Joel5121 said:
What about hardware acceleration? Is Blade capable of it?
Click to expand...
Click to collapse
It's capable of it, but there are still bugs with the way ics uses the drivers. I'm confident that the developers we have working on cm9 for the blade & the other developers working on CM9 for other similar phones will fix it, eventually.
For a discussion of the various X5 hardware specs to determine 'good' builds vs 'less good' builds.
Here are the questions:
What are the hardware differences that contribute to the varying levels of success for Aurora?
What do you have?
Do you have problems with Aurora?
To start, I've got a Synaptec screen; however, what other hardware variations are out there and how do we find out what we have?
And DZO, what do you have?
Point 3. By problems, would u please list the most common one. I never had problems with Aurora other than battery life. But battery life vary for each user in term of syncing, mobile network, app etc.
izzoe said:
Point 3. By problems, would u please list the most common one. I never had problems with Aurora other than battery life. But battery life vary for each user in term of syncing, mobile network, app etc.
Click to expand...
Click to collapse
For this thread to be useful, we should forcibly post our hardware info (better, through some app that eventually generates automatic reports), and then post our specific bugs.
For posting only bugs, there is already the general and the dev threads for aurora, we don't need another thread for that...
With hardware info + specific bug, maybe we can start to find patterns, and that would be of great help for dzo (if he still is working in aurora, of course)...
Sysinfo apk
https://play.google.com/store/apps/...1bGwsMSwxLDEsImNvbS5lbGVjdHJpY3NoZWVwLmFzaSJd
1.. is there any completely working cyanogen mod for galaxy y
2..wat r the bugs in MIUI port
*all cm7 ports have some bugs afaik , most glaring omission was wifi and hardware acceleration ! white has fixed wifi with his compiled drivers and we can expect a release with hw rendition partially fixed soon as broadcom has released test binaries and patches ! that leaves camera(works but white bug), Bluetooth and low sound in headphone as the sole remaining bugs. with cm9 the bugs are more complicated and include no network etc
*afaik all cm7 ports should have more or less same bugs
Bugs in most CM7 Roms
No Bluetooth
Hardware Acceleration (works but not fully ie some high def movies might not work with hw or games)
Low sound in headphones
Wifi - Works but may have to restart phone or use terminal commands to turn back on if switched off in some roms
SD Card - Not all roms can scan sd card for media automatically
Best thing to do is read the bugs list on each op of each rom thread and also user posts for their feedback after testing
Please read the respective thread rather than making thread bro
Sent From Mobile Network
ak.mohanty said:
Please read the respective thread rather than making thread bro
Sent From Mobile Network
Click to expand...
Click to collapse
Who would go through 100 pages of replies
Sent from my Quad-core 1.5GHz 512MB RAM GT-S5360 using xda premium
Mitko said:
Who would go through 100 pages of replies
Sent from my Quad-core 1.5GHz 512MB RAM GT-S5360 using xda premium
Click to expand...
Click to collapse
most of the threads have a bugs list on the first post itself
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
v1nsai said:
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
Click to expand...
Click to collapse
I wish someone could answer this because I'm considering one of the new Nexus devices because I thought I could have this best of both worlds that he speaks of. Is this not the case, do open source driver devices like Nexus phones suffer with the same issues as other unlocked phones that have closed source drivers?
https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel
https://github.com/BalcanGSM/MediaTek-HelioX10-Baseband
Not complete sources.
Just curious, what's missing to be able to build a kernel from that repo?
edit: actually, nvm.
Could someone check sources for Sony Aqua M5? It has the same CPU.
http://developer.sonymobile.com/dow...1-33-30-0-b-1-33-30-0-a-1-35-and-30-0-b-1-35/
Crim Soukyuu said:
Just curious, what's missing to be able to build a kernel from that repo?
edit: actually, nvm.
Click to expand...
Click to collapse
yep, did someone actually check what is missing?
I mean, display drivers .. the drivers for the sensors which are not part of the SoC, such as Lux, camera drivers.. what else?
I am quite sure that looking at the manufacturer´s sites of these components, more drivers, or at least documentation how to drive the components could be found?
Please help to sign this petition
So we can get kernel source for this device.
https://www.change.org/p/xiaomi-inc-mi-com-hugo-barra-release-kernel-source-from-xiaomi-redmi-note-2
Thanks
Sent from my Galaxy Nexus using Tapatalk
How about this? https://github.com/jawad6233/MT6795.kernel
icedeocampo said:
How about this? https://github.com/jawad6233/MT6795.kernel
Click to expand...
Click to collapse
The same. Read the previous messages
~ Xiaomi Redmi Note 2 Prime ~
All these sources are only good to someone who wants to get familiar with mt6795 or MTK in particular,
however just because some source/phone has the same chipset doesn't mean much.
What we're interested in are the drivers and configs for the sensors/components used in a particular device.
So a generic source is of no use if you don't have those drivers and an average Joe can't find them on github,
especially on a new phone which does not share the same sensors as some older device.
Eventually you can get some of the configs by reverse engineering the stock kernel and many many sleepless nights,
but without the actual drivers (or at least something similar that you can base your work on) your hands are tied.
Unless Xiaomi publish the source, we're not going to see a completely working custom kernel, if any at all.
Custom kernel would solve a lot of issues, we can also lower chipset voltage to save battery, increase performance, etc.
Even GPU OC might be possible if it is not fully locked. But that's just in the realm of good imagination at the moment.
In other terms, this is a bare kernel and it is also old leaked pre-release source, I believe full of bugs.
Any news about AOSP 5.1 ?