As Ginger waste my battery too quick, I decided to put Froyo on my Tattoo.
I tried first with [ROM] ProjectSense 0.1 [2.2.1] [Sense], which is going great ... but no radioFM.
As I use FMradio a lot (for football, of course), I have been looking and I found [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version) and flashed it.
After a long search to find a working GAPPS for that rom (I found it at goo-inside.me), I've flashed it, but my phone stucks on trying to access Google's servers, and have no way out of there unless you turn off the phone.
Anyone else with him?
So difícult is making an FM radio app to work in sense? (the only thing missing from the ProjectSense to be perfect)
Do not be a matter of adding a "driver" or library to "activate" the chip, and so run the "Spirit FM Radio", for example?
If anyone has any answer is welcome.
Sorry for my english (Google Translator doesn't help too much)
Flash this gapps they will work.
http://forum.xda-developers.com/attachment.php?attachmentid=424059&d=1287687798
Hit that tiny tnx button if they work xDD
VuK$3 said:
Flash this gapps they will work.
http://forum.xda-developers.com/attachment.php?attachmentid=424059&d=1287687798
Hit that tiny tnx button if they work xDD
Click to expand...
Click to collapse
Thanx. By the moment, i'm gonna use ProjectSense Rom. I'll try later if I need it.
Enviado desde mi HTC Tattoo usando Tapatalk
GbermuG said:
As I use FMradio a lot (for football, of course), I have been looking and I found [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version) and flashed it.
After a long search to find a working GAPPS for that rom (I found it at goo-inside.me), I've flashed it, but my phone stucks on trying to access Google's servers, and have no way out of there unless you turn off the phone.
Anyone else with him?
So difícult is making an FM radio app to work in sense? (the only thing missing from the ProjectSense to be perfect)
Do not be a matter of adding a "driver" or library to "activate" the chip, and so run the "Spirit FM Radio", for example?
Click to expand...
Click to collapse
"Spirit FM Radio" is my app. It doesn't care about Sense.
But for a TI chip device like the Click/Tattoo, it requires a Bluez compatible Bluetooth stack, as is found on CM and some other ROMs.
Also, my app needs a way to turn on the FM audio path. On a Sense based ROM this might be the "HTC" Audio Method that needs to be configured.
mikereidis said:
"Spirit FM Radio" is my app. It doesn't care about Sense.
But for a TI chip device like the Click/Tattoo, it requires a Bluez compatible Bluetooth stack, as is found on CM and some other ROMs.
Also, my app needs a way to turn on the FM audio path. On a Sense based ROM this might be the "HTC" Audio Method that needs to be configured.
Click to expand...
Click to collapse
I supose the problem is ar bluetooth stack, as you say, because ProjetcSense isn't a CM based rom. I installed your app, and configured audio method in all the posibilities, included "HTC", but it's allways saying me "compatible chip not found", or something like.
Today I'm gonna make a backup, an change some files from other Froyo Rom with FMradio working. Another thing I'm going to try is changing some values in build.pro, cause this Rom has BT chip identified as BCM4329-B1, but I read in some threads it's a different one.
Thanks anyway.
The exact message is:
"Sorry, compatible FM chip not found...
FM:TI Sh:1 Su:1 Bt:0 Ht:0 H2:0 M0:TIU"
I think it means.. "FM chip is TI, but BT is 0, so I can't make it works". And now, th question is... why BT:0, if Bluetooth is on?
I was cooking a sense 2.2.1 ROM and I made everything work except FM radio.I fond mikereidis thread about TI chip but i was unable to enable it
When I try shell command it always says access denied....
Any ideas ?
Something has changed.
I tried to use the fm_script by cm.fyodor, and when I wrote the comman at Terminal CMD, I receive many lines resumed on two: "bttest: not found" and "hcitool not found".
Looked for the files at Fyodor's [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version), and found them at /system/xbin. So, I'd copy the files to my phone, and retry the "Spirit FM Radio".
But the message I had (2nd line) now is "FM:BC Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:BCU".
After it, I edit settings->debug and check "Use fm_hcitool" and set FM chip to "Automatic", but app is still not working.
I've deleted info about BT chip in build.prop. Now, when I try to execute fm_script, the message is "HCI command: XXXXXX Send failed: File descriptor in bad state". Back to previous build.prop, same message: "Send failed"
I'll keep on trying things...
I'm pretty sure this device uses a TI chip for FM, BT and WiFi. My app, and the script that I think came from me originally, was working on this device back when my app generally only ran on the HTC Legend. I think these are the only 2 HTC devices using the TI chip.
Yes, I think the problem is that stock HTC ROMs use the Broadcom or TI proprietary Bluetooth stack. So just about anyone making a Sense based ROM uses that same stack.
"Send failed: File descriptor in bad state" happens when trying to use hcitool with the proprietary stack. (But can also happen with other fatal errors that are fixed by restarting BT.)
If I am correct, then I'd think the HTC FM app would work. Is there a btipsd process running ? That's the proprietary TI stack. On the Legend, there is a btipsd_cli binary that my app can use with this stack. I don't think anyone by myself has ever used this mode, LOL.
Here's the binary if you want to try. The btipsd version might need to match somewhat though: http://www.mediafire.com/file/p0w159ubto2frw6/btipsd_cli.zip
If you copy files from a Broadcom based BT device, then you can confuse the automatic FM chip detection, which is why I think you saw "Mo: BCU" (Broadcom unknown.) You can force to TI still.
Changing audio method won't help until we can see RSSI and seek working,
So, options:
- There's likely some way to run the HTC FM app for Tattoo/Click or Legend if the TI stack.
- My app will work with Bluez stack
- My app might work with btipsd in the TI stack via btipsd_cli.
- I may at some point support a "direct to BT UART mode" that works with BT off, as I have for Broadcom chips.
- I'm also looking to support the Broadcom and TI stacks more directly, but this likely won't happen for several months at least.
GbermuG said:
The exact message is:
"Sorry, compatible FM chip not found...
FM:TI Sh:1 Su:1 Bt:0 Ht:0 H2:0 M0:TIU"
I think it means.. "FM chip is TI, but BT is 0, so I can't make it works". And now, th question is... why BT:0, if Bluetooth is on?
Click to expand...
Click to collapse
This part of my code doesn't care whether or not Android thinks BT is running.
If any of the following processes are running, it will show "BT: 1":
For Bluez BT:
hcid
bluetoothd
hciattach
For TI proprietary BT:
btipsd
For Broadcom proprietary BT:
btld
brcm_patchram_plus
Ok, this is starting to go!!!
I copied your file (btipsd_cli) to /sistem/bin, and after a reboot, start your app. First time, it doesn't work, so I changed settings->debug->FM chip to "Tex Instr (Motorola)", and... Voila!! THE APP IS WORKING!!! But no audio.
The text strings I can see are:
- 0 Aud?
- PI: -1
- Fm:TI Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:TIB
mikereidis said:
This part of my code doesn't care whether or not Android thinks BT is running.
If any of the following processes are running, it will show "BT: 1":
For Bluez BT:
hcid
bluetoothd
hciattach
For TI proprietary BT:
btipsd
For Broadcom proprietary BT:
btld
brcm_patchram_plus
Click to expand...
Click to collapse
After many tries, I noticed this rom got "btld" file ( Broadcom propietary), but no "btipsd" other than btipsd_cli file i've copied.
I'm sorry, but i've no skills enough to understand "processes"...
And... yes, BT:1
I'm still thinking something is wrong in build.prop with BT chip identification:
" # release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.47.005
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339"
Why "ro.bt.chipset= Broadcom BCM4329-B1", if it's TI???
GbermuG said:
Ok, this is starting to go!!!
I copied your file (btipsd_cli) to /sistem/bin, and after a reboot, start your app. First time, it doesn't work, so I changed settings->debug->FM chip to "Tex Instr (Motorola)", and... Voila!! THE APP IS WORKING!!! But no audio.
The text strings I can see are:
- 0 Aud?
- PI: -1
- Fm:TI Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:TIB
Click to expand...
Click to collapse
Woohoo !
I've had this "weird" btipsd mode in my app for probably 6 months now and you're the first to report using it. I'd been considering removing it, since it has various problems.
Did you try all the different Audio Methods under Menu -> Settings -> Audio ? You can tune a good station and stay in that config screen trying them all.
Most likely to work I think is the HTC method, although one of the strangely named methods like msm7x30 may work.
Send me a log and I can look. Select Menu -> Help -> EM Logs.
GbermuG said:
After many tries, I noticed this rom got "btld" file ( Broadcom propietary), but no "btipsd" other than btipsd_cli file i've copied.
I'm sorry, but i've no skills enough to understand "processes"...
And... yes, BT:1
I'm still thinking something is wrong in build.prop with BT chip identification:
" # release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.47.005
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339"
Why "ro.bt.chipset= Broadcom BCM4329-B1", if it's TI???
Click to expand...
Click to collapse
Yes that's rather strange. I can't imagine you have a Tattoo/Click variant with a different chip.
I've been seeing more "universal" ROMs lately that have files for both Broadcom and TI. This makes my automatic chip detection fail sometimes, so I created the Settings -> Debug -> FM Chip option to force a chip type.
Send me a log and I can look. Select Menu -> Help -> EM Logs.
Thanks !
mikereidis said:
Yes that's rather strange. I can't imagine you have a Tattoo/Click variant with a different chip.
I've been seeing more "universal" ROMs lately that have files for both Broadcom and TI. This makes my automatic chip detection fail sometimes, so I created the Settings -> Debug -> FM Chip option to force a chip type.
Send me a log and I can look. Select Menu -> Help -> EM Logs.
Thanks !
Click to expand...
Click to collapse
I can't imagine it too. I got installed a CM7 rom with Gingerbread, and your app works perfectly.
I've tried installing HTCMusic.apk from a Donut Sense rom (this app controls both music and FMradio), but gives me a FC (I supose it's normal). I've tried to install FM.apk from an AOSP Froyo rom, but it doesn't work too.
I've sent the log. Thanks for your dedication.
GbermuG said:
I've tried installing HTCMusic.apk from a Donut Sense rom (this app controls both music and FMradio), but gives me a FC (I supose it's normal).
Click to expand...
Click to collapse
Normal ? Well something is missing or wrong.
Assuming your BT stack is proprietary from TI, I'd bet you could run the FM app from a stock Legend. It's just FM, no music. But I'd rather you run my app....
GbermuG said:
I've tried to install FM.apk from an AOSP Froyo rom, but it doesn't work too.
I've sent the log. Thanks for your dedication.
Click to expand...
Click to collapse
I'm not aware of any AOSP ROM with an FM app. That would mean Google source code for an FM app and I've never seen any,
I haven't seen any log email from you. Perhaps it didn't go through or I don't know which email is yours. You could just send me the /sdcard/*.txt files that came from my app.
After I received your mail, I noticed something I didn't give any importance in the past: this Rom is ported from HTC Wildfire!
So, I think the dev "mixed" files to make BT work.
I'm gonna try some file changes, and tell what happen.
Enviado desde mi HTC Tattoo usando Tapatalk
GbermuG said:
After I received your mail, I noticed something I didn't give any importance in the past: this Rom is ported from HTC Wildfire!
So, I think the dev "mixed" files to make BT work.
I'm gonna try some file changes, and tell what happen.
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
And the Wildfire has Broadcom BT/WiFi/FM. Makes sense.
So the ROM will need some additional files, like TI's btipsd, and the startup file(s) will have to initialize the TI BT.
With the ROM you have now, Bluetooth can't work. Make it work with btipsd and my app may work in the TI btipsd mode. I think your apparent previous success in this mode was false.
I'm afraid so. I have no bluetooth device to check it.
I've spent some hours on selecting files from a Legend's Froyo Sense custom Rom, and after paste them on my phone, the only difference is your app isn't showing the "Aud?" string (but, of course, there's no audio).
I'll continue tomorrow.
Enviado desde mi HTC Tattoo usando Tapatalk
I tested Bluetooth on TatFroyoSense,it sometimes work and sometime not...so u must restart phone to work again ,and u cant transfer bigger files becaouse it stops working...
Related
Disclaimer: I am not responsible for any damage (including, but not limited to, loss of data, non-functional device etc.) which may occur to your device from following the directions (or from any failure to follow the directions) found on this post. Use (and flash) at your own risk.
Credits go to genokolar for actually porting the U8860 2.3.6 firmware to the U8800Pro. This builds upon his port.
You may find his port announcement here, and you can download it from here. Thanks to user Skyline111 for the mirror.
Thanks also go to birdyi, who ported the U8860 2.3.6 firmware to the U8860. His port contained some brilliant things such as CarrierIQ framework removal.
--
This is a 2.3.6 ROM for the U8800Pro based on the U8860 B866 ROM. 2.3.6, naturally, brings a slightly newer version of Gingerbread compared to our 2.3.5 with B540. While I know it's all about CM9 (ICS), MIUI and so on these days, I'm a fan of stock (in the Huawei sense of the term) Gingerbread.
Features (or limitations depending on what you think of some of the following entries) of this ROM:
Rooted (adb also runs as root, too)
(Huawei) DLNA
(Huawei) A task manager that shows open applications with pictures (launching it when pressing Home has disabled in this modification because I found the Recent menu saves more time)
(Huawei) Security Guard, a way of hiding text messages, I think
(Huawei) Traffic Manager – a data counter
(Huawei) Wi-Fi WPS support
(Genokolar) FPS unlocked by default (configurable in enhanced.conf)
(Genokolar) ZRAM (Compcache) enabled
(Genokolar) Changed the autorun.iso path to the image partition so that formatting /data from CWM does not leave you with an empty CD-ROM drive when you plug the phone into a computer
bugreports service turned off entirely so that pressing the volume up button quickly after you've pressed volume down does not leave you with a few seconds' delay and a bugreports folder on your memory card
BusyBox from CM7
Android’s toolbox (poor coreutils replacement; more barebones than BusyBox) has its full set of links installed in /system/bin, so you use Android’s native chmod etc. tools. Why? To match the stock B512 firmware and to ensure developers testing on the U8800Pro correctly hardcode “busybox” in their root programs if needed
Optional lazy CPUfreq governor
Default language and region changed from Chinese – China to English – United Kingdom
Added in boombuler’s AppWidgetPicker
CM7’s Pacman added in to remind you to install Google Apps after adding an account with the Setup Wizard (make sure GApps is installed!)
VoiceDialler.apk added in from B512 firmware (although, to be honest, the microphone quality on my phone is awful…)
Bash shell, fix_permissions script, iwmulticall, MMS.apk, tcpdump and gdbserver and additional ringtones etc. from CyanogenMod (20120107-cm-7.1.0-u8800pro-Geno-en.zip) added in
Phone model changed to Desire HD, so Gameloft games can be bought. This may cause licensing problems with bought Market applications so be careful. (Although, I must admit that giving money to a company that doesn't support our phone seems counter-intuitive.)
Shutdown vibration reduced from 500ms to 100ms because I hate it (especially at night) but understand its usefulness in determining the answer to the question “Has the phone gone off yet?”
Huawei’s god-awful Low Battery notification replaced with a nicer one from CyanogenMod
Widgets actually restore themselves after a reboot! This was fixed by me replacing 2.3.6's PackageManager service with Huawei's 2.3.5 one.
MyCalendar widget from birdyi's port and MyEmail from B512 added in
Fixed proximity sensor dying if the light sensor was on, too.
Stripped down enhanced.conf - only swappiness, VSync and ZRAM settings available. I don't like /system/log.txt being created every time my phone boots and I think using a tool in Android like, say, No-frills CPU Control is the better place to set the frequency. SetXperia has support for setting the phone's CPU voltage.
More languages selectable from the Setup Wizard than just English (US) and Chinese.
Flash Player removed for copyright reasons. You can install it from the Market
Notepad and Richpad removed
Droid Sans Fallback supports more character ranges
Toolbox correctly has "Wi-Fi" instead of "WLAN"
Misc. kernel modules, like in B512, included
But I like the BusyBox tools and want to use them without having to prefix BusyBox everytime!
Just run the bash shell; BusyBox versions of cat, chmod, chown, df, insmod, ln, lsmod, mkdir, mount, mv, rm, rmdir, rmmod, umount, sleep, kill, and ifconfig will become the default while you’re using the bash shell (also nicer, BTW: you get tab-completion, for one) thanks to the CyanogenMod team.
Attempts to remove Carrier IQ. Huawei *do* include Carrier IQ in their firmware.
I’ve done the following to attempt to remove it the best I can:
Edited boot.img to not start Carrier IQ services
Removed Carrier IQ libraries from /system/lib and CiQ binaries from /system/bin
Added lines to build.prop to disable CarrierIQ, taken from the framework.jar file itself.
birdyi has also modified framework.jar to stop the CarrierIQ objects from being instantiated.
Ideally the best way to be Huawei-free is to use CyanogenMod.
I've removed the Cloud+ apps because of this. I've left some Huawei apps in, but I strongly recommend you install PDroid (the patcher works fine with this ROM) and block the more concerning permissions of Huawei system apps.
Kernel changes
Since the kernel genokolar provided with his port had a problem when a program used the light and proximity sensor at the same time – the proximity sensor would die out until the next restart – I took it upon myself to rebuild the kernel available from his github repository with the config from his latest kernel. After comparing his kernel to the source Huawei put out, I could see no code changes that would cause the proximity sensor to die out. Since I was rebuilding the kernel, I thought I’d make a few changes:
Add in the Lazy CPU governor by Ezekeel
Update a patch by stockwell to disable keypad lights (echo 1 > /sys/module/leds_msm_pmic/parameters/disable_button_leds) - use ButtonLock to control
Reverse genokolar’s decision to always allow NV logging – this can be turned on and off from the service menu on a stock ROM anyway…
Set minimum backlight level to 15, from Franco’s kernel. Warning: I haven’t tried setting it to 15 so I don’t know if that value renders the display practically useless, and I don’t know if Android lets you set it to 15 from its settings!
ButtonLock
Not as revolutionary as I'd like it to be, but useful nevertheless. I've written a quick widget, which looks like the Power Saving one, that turns off the button backlight. Useful for when you're reading books through FBReader.
You need to be using my kernel as it has the disable_button_leds patch. The advantage the disable_button_leds patch has over the chmod 444 method is that it doesn't introduce noticable lag. The widget's source is in the same folder.
When pressing the widget's button for the first time, there is a delay as the Superuser allow/deny dialog box takes its time to come up. After accepting, future launches are instantaneous.
If you need something that this ROM doesn’t provide compared to other stock ROMs, I recommend:
Not using it; or
Using a combination of diff, abootimg, Winmerge (or Beyond Compare) and apktool to compare this with genokolar’s original release, and with birdyi's ROM, and add what you want back in
Installation
Note: You must be running firmware version B522 on your device! If you have B540, you need to downgrade. If you have a firmware version lower than B522 (Froyo?), you must upgrade to B522 first. If you're already running a custom ROM, ignore this.
Take out the SIM card if you want the setup wizard to use Wi-Fi during setup.
Install genokolar’s recovery: http://forum.xda-developers.com/showthread.php?t=1343276
Place u8800pro-2.3.6-geno-v1-modified.zip on the internal memory card or an external one (I recommend the internal one to ensure you don’t run into U8800Pro CWM bugs with the external).
Get gapps for Gingerbread and place on your memory card. Find the link using every Android user’s favourite search engine.
I highly recommend using PDroid, but it’s up to you whether you want to use it. If you would like to use it, get the patcher from http://forum.xda-developers.com/showthread.php?t=1357056 and point it to u8800pro-2.3.6-geno-v1-modified.zip. Place the PDroid-v1.27-u8800pro-2.3.6-geno-v1-modified.zip file onto your memory card.
Boot into recovery (make sure that fast boot is turned off in Settings->Applications and hold power and volume up while turning the phone on)
Do a data/factory reset.
Install the ZIPs, starting with u8800pro-2.3.6-geno-v1-modified.zip (obviously).
Reboot!
Install the Google apps (those ones not included in CM's gapps ZIP like YouTube) if desired when prompted – but note that the Market will probably close as you’re doing this as it will automatically update itself.
Downloads
ROM: http://www.mediafire.com/?k0g17z1kraw7b67
SHA512: 4988B123488B8B24732401420DE849E8D8E5632C075A4520F176AA1D64DA0ECF946FF4D4E6CEC4D257EE4C4C999200A93C2CB309FD7B5FE50234A1C5700DEB2D
Modified kernel source (I suck at Git - I really need to read that VCS by Example book I have ): http://www.mediafire.com/download.php?a0022t73q2v7r7d
ButtonLock source (Apache licensed, though I must admit I'm more of a GPL person...): attached.
--
Extras:
genokolar's 5.0.27 recovery for the U8800Pro with the charging animations from https://github.com/Victor-android/android_device_huawei_u8800pro/tree/master/recovery/res/images:
attached.
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Too times was a situation, when phone lost connection with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
...
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
bobsido said:
with wi-fi spot, he see the network, but can't connect. Help reboot.. else working so far without problems, testing..
Click to expand...
Click to collapse
Interesting. I've had no problems reconnecting to a network that uses WPA2-PSK and another that uses 802.11x authentication.
turned off the wi-fi and got the main bug - does not work 3g/2g data transfer, hmm....
Click to expand...
Click to collapse
Are your APNs set correctly? In my case 2G works and I've had HSDPA working because when testing the Weather Clock widget (from B522, when I had it in) it would connect using it - I could see the icon in the status bar - and I had the pleasure of having my balance run down each time - I'm not a rich man
Edit: In build.prop, you can try playing with ro.config.hw_fast_dormancy=3 - genokolar had it set to 2, but I changed it back to 3 from the U8800Pro original ROM because I wouldn't be able to connect to my network otherwise.
Hopefully, it's not the case but it could be hardware differences. genokolar, who's work this is based on, being from China, probably has a Unicom U8800Pro, just like I do...
@Zaic
B512? This is for the U8800Pro. I'd advise you not to flash it. I'd recommend using birdyi's ROM. If you're after a certain improvement from this ROM, tell me and I'll try and isolate it for you (as long as it doesn't involve kernel stuff - I don't know how to build U8800 kernels) so that you can use with birdyi's ROM
I have u8800 pro - 100%
My ROM is original unrooted 2.3.5 B512 its one before the latest release which is B540
My ROM still has access to pink screen, otherwise its the same as B540 I guess
SO what should I do first to install this ROM? roll back to 2.2.2 or was it 2.2.3?
Ah, if you're running 2.3.5 already and in the pink screen mode you see a folder called image when connecting your phone to the computer you're ready to go
Hi!
My compliments for the porting of Android 2.3.6 to U8800Pro!
I am using your rom since yesterday and still now I am not having any kind of problems.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Please try to reproduce this bug.
I am using LauncherPro but this bug is indipendent by the launcher (for example I tried also Zeam Launcher, Go Launcher EX, etc etc).
I hope you can solve this bug, maybe kernel-related.
Regards,
kalo86
Hi,
kalo86 said:
My compliments for the porting of Android 2.3.6 to U8800Pro!
Click to expand...
Click to collapse
The honor is genokolar's
I am using your rom since yesterday and still now I am not having any kind of problems.
Click to expand...
Click to collapse
Thanks; it's nice to know that it's working OK on somebody else's device other than mine.
Anyway I notice the same bug of the B512 and B540 roms: put your smartphone on screenoff, then wait about 1 minute and fastly unlock the screen and try to pinch to zoom on the home. Sometimes the multitouch doesn't work on every position of your fingers, it only works correctly if your fingers are in the position of principal axes.
Click to expand...
Click to collapse
Sorry for asking, but how do you pinch to zoom on the home screen? I'm using Go Launcher Ex and I know that that has the swipe up gesture but I can activate that with one finger, anyway.
In any case, have you applied the Synaptics touchscreen update? For me it has increased the touchscreen performance greatly. I had one problem that when after unlocking, the touchscreen wouldn't respond unless I turned the screen off and tried again. The update solved that.
If you want to try it, open the service menu (*#*#2846579#*#*), go to ProjectMenu->Upgrade->Touch screen version query and see if it says "synaptics". If so, put the original Huawei recovery.img back on and put the synaptics.img file in a folder called update on your SD card. Use the recovery's "touchscreen firmware update" update option and it will automatically reboot when it's done.
Best regards,
qwerty12
Oh, really thank you for this "news" about the synaptics touchscreen update!
I have a synaptics too, then I am going to update the firmware.
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Thanks to You and Genokolar for our development!
Regards,
kalo86
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Video demonstration
This is a video which I just uploaded on YouTube with the real multitouch bug.
This bug is in 4 different U8800 Pro.
http://www.youtube.com/watch?v=avSdW2V8TLg
kalo86 said:
Another bug, still present in B512, B540, Cyanogen and U8860 port: unplug your battery from the smartphone, insert it again, power on, then open your file manager and try to read the sdcard content. At 99% my sdcard is not read, then I have to reboot my U8800Pro and magically the sdcard is read.
Click to expand...
Click to collapse
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
UPDATE: I updated the synaptics touchpanel but I have always the bug of multitouch. It is reproducible when you unlock the screen after a pause of 1 minute (about), then you open the stock browser and try to zoom with the multitouch. It works only if your fingers are on the principal axes and not in other positions. I have this bug on 4 different U8800 Pro! It cannot be a singular problem.
So, I have tried a lot of roms, based on B512, B540, U8860, CyanogenMod 7.1, I am sure I will try this bug on the next release because it's mabe a kernel bug due to the multitouch field.
Click to expand...
Click to collapse
Thanks for the video! Unfortunately I don't know how this can be fixed - I'm not a developer! It was only yesterday I tried looking in the driver to see how I can enable more than two finger recognition but I'm not seeing it...
Best regards,
qwerty12
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
qwerty12 said:
I really can't reproduce this. I pulled out the battery while it was on, put it back in and started File manager (the one included with Huawei ROMs) and the internal SD card along with my external one were seen fine.
Click to expand...
Click to collapse
The same here with sd,full power off device, power on then sd card is not mounted and cpu load is almost 100%. after restart or reinserting sd, problem just dissapear. on every rom i tried. i flashed official V100R001C00B512G001Gb (2.3.5) and then tried CM7; u8800+v100r001c00b540g001gb-rooted_geno-v4.
Is FM Radio working in this ROM?
Yes, Radio is working fine
qwerty12 said:
Are your APNs set correctly?
Click to expand...
Click to collapse
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
kalo86 said:
Sorry for disturbing you, but I have a question: do you have the same bug of the multitouch after the lock-screen?
This is a second video about the same problem:
http://youtu.be/64NvbFJD3rs
Click to expand...
Click to collapse
A little bit - after unlocking, I can do the multitouch gesture and phone will respond like it's supposed to but I have seen twice that it has not responded to me; I have to do it twice more...
Barracuda72 said:
Is FM Radio working in this ROM?
Click to expand...
Click to collapse
Like kalo86 said, it is indeed
bobsido said:
i fix APN settings and 3g/2g start work, thanks.. after reflashing wi-fi start work without problem. but after first reflash don`t work home button. they have response, but nothing happen. i secondary reflash phone, without wipe data/cash and home button start to work correct.. now tests are continuing
Click to expand...
Click to collapse
Please do let me know if you come across more problems
Zaic said:
Anyone tried it?
ill try it this evening I hope it fixes missed calls....
I have B512 official gingerbread, am I good to go?
Click to expand...
Click to collapse
So, any missed calls?
If someone wants to help the Community to understand the sdcard mount bug, please have a look here: http://forum.xda-developers.com/showthread.php?t=1483519
This is a poll, please vote!
Best regards,
kalo86
Zyzas said:
So, any missed calls?
Click to expand...
Click to collapse
Haven't had time to install this ROM yet.... but ill report as soon as I know
Last edit
DZO original disk : http://sourceforge.net/projects/icsaurora/files/ ( Please download the original to support the original author of DZO, I do not brush the card
birdyi at 2012-3-4 17:21
encrypt packets, or a brush with variable false brick ) http://code.google.com/p/ics-aurora/downloads/list, not carefully look at the post ( this is the DZO's network drive, the original with localized versions it is not the same, we all experience authentic ice cream ) series updates the original: http://bbs.anzhi.com/thread-4889690-1-1.html DZO Update Description: of DZO Big God 1.12 No one was translation? I ~ localized versions of changes to spending more time for the difference between the original: (Knight version will be much more, we wait. ) Huawei File Manager can directly browse the built-in card . call current tone correction (aurora_1.12a original setting options, the next version will be canceled this default, the independent set) 3 built-in radio to replace Huawei radio streamline the google framework services, will provide a complete card brush package 5 can be performed manually fps unlock with their own re Manager to enter the system / sbin / gk the ninth script can manually switch to the second system (if you installed a dual system of words), enter the system comes with re Manager / sbin / gk eighth script execution, the next version to consider doing a dual system adapter 7. search button changed to off-screen, volume up and down keys can be lit screen . models U8800 without modification, manufacturers point to the HTC (TX reaction now without changes, the next version to consider recovery) 9. remove the boot need to do a series of set the language automatically for the Chinese time zone default Dongba not default original framework and APK odex of So brush machine first start after slow 11.8800 + / 8800PRO also can brush, but the wifi Bluetooth does not work 12.GPS positioning server changed to Asia to accelerate the positioning suite of Google services: need Google services directly to brush package framework to provide a card, the card brush package default Google service framework integrated sync contacts calendar synchronization, Google backup, e-mail, not integrate Twitter, youtube and other needs over the wall in order to use the program, you need other apk from the original extract apk directly dragged into the system / app under card brush can.
This is only for testing..the rom is pretty much stable but until now noone can fix the wifi,bt problem...we're waiting for dzo or genokolar or someone else!!
http://www.mediafire.com/?3b68daoknffftu6
Shouldn't be too hard to port wifi/bt drivers, using zImage from geno's kernel and correct modules in /system/lib, but dunno if ICS has another way to handle modules and kernel drivers, some dev may help with that
sewa2k said:
Shouldn't be too hard to port wifi/bt drivers, using zImage from geno's kernel and correct modules in /system/lib, but dunno if ICS has another way to handle modules and kernel drivers, some dev may help with that
Click to expand...
Click to collapse
Until now noone cant they say they need dzo to fix this maybe its fixed before compile but if you know you can give it a try many ppl will thank you
Sent from my U8800Pro using Tapatalk
aurora_1.13 is out
http://115.com/file/anfwja4q
As genokolar said to his microblog tommorow he will release ics 4.0.3 working wifi+bt!!
WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other
Exclusive MODDED ROM EQS-v2.0M
CS968 a RK3188 ChipSet Based TVBoX
AKA: TV01 [GeekBuying] CR11s [CloudNET2GO]
THIS VERSION HAS NATIVE 1080P KERNEL, NOT SAME AS V1.
IMPORTANT INFORMATION:
WE JUST LEARNED THERE ARE A FEW CS968/TV01/CR11s MODELS equipped with different WIFI/BT MODULES.
Thanks to dFenix we figured this out. [More info]
THIS ROM IS FOR AP6210 WIFI CHIP bundled devices, MAINBOARD VERSION 2.
So if you try this rom on other models you may loose your wifi connection.
Click to expand...
Click to collapse
IMPORTANT NOTICE:
THIS IS KIND OF BETA/ALPHA FIRMWARE OR WHATEVER YOU WANT TO CALL IT.
CURRENTLY I HAVE EXPERIENCED NONE PROBLEM AND IT SEEMS EVERYTHING INCLUDING 1080P MODE WORKS FINE.
THIS IS AN EXCLUSIVE ROM BECAUSE THERE ARE A FEW THINGS FACTORY FIRMWARE HAS NOT.
SYSTEM IS SAME AND NOTHING HAS BEEN MODIFIED EXCEPT SUPERUSER and BUILD.PROP, SO IF THERE IS A BUG THEN THAT IS FIRMWARE RELATED THIS ISN'T SUPER DUPER FIRMWARE AND DOESN'T HAVE SPECIAL KERNEL OR RECOVERY, EVERYTHINGS IS STOCK.
NOTE : LIBMEDIA.SO REPLACED, READ BELOW...
Factory Date : 09-12-2013 from CloudNET based CR11/s
Modification Date: 21-12-2013
NOTICE: THIS IS FOR 2 MPX VERSION, NOT FOR 5 MPX
You may harm your device, if you flash this firmware to 5 mpx camera version.
LCD Display density has been set to 240, if you need smaller icons and texts you can easily change by using preinstalled DPI changer program (May need root permission after first start).
Features:
Rooted [ You may notice a bit difference than v1 version, but it is normal ]
Build tweaks
TCP Tweaks (Buffering etc...)
Networking Tweaks
Wifi Tweaks (Signal etc...)
Multimedia Tweaks
Streaming Tweaks
HW Video Acceleration by default
Spoofed as Galaxy S3
Date format set to European
Timezone Europe GMT +1
Renewed bootanimation
Renewed wallpaper
Add: SuperSU.apk (Updated)
Add: LuckyPatcher (Updated)
Add: RootBrowser (NEW)
Add: OGYoutube with downloader [ Original YouTube still can be apartly installed ]
Add: Dolphin Browser 10.1.2
Add: Android Weather
Add: JetAudio
Add: Blueput Droid (NEW)
Add: Texdroider DPI (NEW)
Add: BSPlayer FREE (NEW)
Add: Cifs Manager (NEW)
Add: ESFile Explorer (NEW)
Add: Patched Libmedia.so (Many thanks hillyu from FreakTab, More info)
Updated : AddAway (Update)
Removed : All of useless chinese media stuff
Removed : Chrome
Removed : Search Box
Removed : Google Stuff (Search, maps, gmail, talk)
Removed : Email
Removed : XBMC Installer (Not everyone's taste)
Removed : A few more crap...
Exclusive test modules : Tun, Cifs*, NFS, NTFS and Xpad these modules are not installed by system, must be done manually from console/terminal.
Included CIFS MANAGER can do it for you, you don't need to install from terminal.
Exlusive bootanimation (Renewed)
Good working Remote Control.
Faster Internet browsing, smoother streaming, Very nice playing 1080p media from NAS DRIVE
*: It seems cifs module won't work properly, it is interesting because it was allright with K-R42 device but I'll search for it.
v2.0M CHANGES
NEW*: MultiWindow
*Needs Xposed Framework to be installed completely.
NEW*: Xposed Framework Installer
*Installation must be done via program self, then after reboot you may download modules as much as you want
REPLACED : BSPLAYER-> MX PLAYER FREE - No Codec pre-installed
REMOVED : JETAUDIO
UPDATE : LUCKY PATCHER, ADAWAY
UPDATE : DOLPHIN BROWSER 10.2.1
Re-Add : RKVideo player, RKExplorer
A few fixes that causes problems.
More optimized video playback (about 40 mbps mkv from network drive), more stable system.
LCD Density set to : 160 (Smaller icons and texts by default)
A little bit faster than 2.0 version.
Feel free to test or build new one, no words for future updates or versions etc.
FLASH WITH YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING OR AFTER.
AnTuTu Results
Devhost / Mirror
password : cs968eqs
Firmware flashing guide.
[ HD QUALITY BOOT ANIMATIONS... ]http://forum.xda-developers.com/showthread.php?t=2612221
hi
Hi Equancy,
Is a small community of CS968 users here: freaktab.com/forumdisplay.php?165-CS968-CR11s-amp-similar-sticks
Would you like to share this rom there too?
fakotibor said:
Hi Equancy,
Is a small community of CS968 users here: freaktab.com/forumdisplay.php?165-CS968-CR11s-amp-similar-sticks
Would you like to share this rom there too?
Click to expand...
Click to collapse
Hi,
Yeah, it seems not much users have CS968 here in XDA but, I'm a member of XDA-Dev and I share what I have here, but you may share this thread on freaktab as yours if you wish.
I have no account on FreakTab and I don't think I may able to manage this thread on multiple forums.
So, I can answer questions only here and also publish updates of my rom.
Thanks for your interest.
Hi Equancy, I cant download this file.
(Error no: 1) Connection failure : User 'proxy_iamheman' has exceeded the 'max_user_connections' resource (current value: 10)
What seems to be the issue. please fix the link. Thanks.
resansid said:
Hi Equancy, I cant download this file.
(Error no: 1) Connection failure : User 'proxy_iamheman' has exceeded the 'max_user_connections' resource (current value: 10)
What seems to be the issue. please fix the link. Thanks.
Click to expand...
Click to collapse
Try primary download host (Devhost), its working flawlesly.
I guess mirror host has problem rightnow.
I've uploaded another Mirror-link working well.http://www.filedropper.com/showdownload.php/cs968051213eqsv2m
EQUANCY said:
Try primary download host (Devhost), its working flawlesly.
I guess mirror host has problem rightnow.
I'll make more mirrors soon.
Click to expand...
Click to collapse
OK This worked. Thanks.
resansid said:
OK This worked. Thanks.
Click to expand...
Click to collapse
Your welcome. :good:
Or you may try from here too.
@EQUANCY,
i tried your rom, looks good. few things are not wrking
1. xposed: i installed xposed framework, rebooted, then installed GravityBox, none of the tweaks in it wkrs. like transparent status bar/traffic meter.
after installing the GB and setting it up, i rebooted, but still not wrking.
2. window support is also not wrking. hv added some of the apps to wkr in window mode, but all run in full screen.
Have you tried these on ur rom ???
hanu_blr said:
@EQUANCY,
i tried your rom, looks good. few things are not wrking
1. xposed: i installed xposed framework, rebooted, then installed GravityBox, none of the tweaks in it wkrs. like transparent status bar/traffic meter.
after installing the GB and setting it up, i rebooted, but still not wrking.
2. window support is also not wrking. hv added some of the apps to wkr in window mode, but all run in full screen.
Have you tried these on ur rom ???
Click to expand...
Click to collapse
Yes,
Multi-window not working, but some features of Gravitybox well.
Actually I've put Multi-window by mistake, it was a bit late when I saw
However you may remove this app by following steps below.
1- Deactivate Multi-window app in Xposed modules menu (uncheck)
2- Reboot
3- Open RootBrowser and go to System/app directory
4- Long press on multi_window.apk and select Delete
I didn't tested all of modules and most of them are not working properly because of Tablet UI, I'll remove both application in next firmware mod.
Sorry for inconvenience, thanks for understanding.
Hi Equancy,
I am having issues with wifi direct. I can establish the wifi direct connection with the other device (Samsung Galaxy S3) just fine, I can send files from the box to the SG3, but I absolutely can't receive files sent from the SG3 to the box (I never even get the prompt).
I also tried to use the Superbeam app, and same story: I can send files out but not receive them.
Any clue? I am not sure whether this is specific to your ROM as I haven't tried with any other.
Cheers, Merry Christmas and Happy New Year to you.
daviddema said:
Hi Equancy,
I am having issues with wifi direct. I can establish the wifi direct connection with the other device (Samsung Galaxy S3) just fine, I can send files from the box to the SG3, but I absolutely can't receive files sent from the SG3 to the box (I never even get the prompt).
I also tried to use the Superbeam app, and same story: I can send files out but not receive them.
Any clue? I am not sure whether this is specific to your ROM as I haven't tried with any other.
Cheers, Merry Christmas and Happy New Year to you.
Click to expand...
Click to collapse
hi,
Thanks for your best wishes, hoping same for you.
For the issue,
Possible answer for WiFi Direct function is Firmware related, because I didn't touched any system file except su binary and build.prop.
I also tested by my self, receiving files from TVBox is working but transfering to the device isn't via SuperBeam.
As I said before, I suppose it is a firmware bug and must be reported.
And question is:
To who
However, you may ask other users who is using another firmware versions or custom roms.
Happy new years...
NFS help needed
I tried the rom on my cr11s and i must say its awesome except that its a bit slow.. i also can't get nfs to mount thru adb nor cifsmanager.. does the supplied nfs.ko support nfsv4? Everything else is working with no major issues.. thanks for the rom anyways...
PsychicSaint said:
I tried the rom on my cr11s and i must say its awesome except that its a bit slow.. i also can't get nfs to mount thru adb nor cifsmanager.. does the supplied nfs.ko support nfsv4? Everything else is working with no major issues.. thanks for the rom anyways...
Click to expand...
Click to collapse
It is very little bit slower than v1.1 but its not really noticable on 2D applications, can you specify what have you experienced actually?
I'm using a NTFS formatted NAS drive with no problem, even watching MKV files about 40-50 mbps rate. (NetGear ReadyNAS).
All of thoose modules have been supplied but not loaded by default need manually installed or you must add lines to the init.rc from system.
This can't be automatically because Kernel needs to be modified and I don't want to do that.
NFS module is actual module for RK3188.
If you more specify problem may be I can look it for you.
And for your consideration...
Some issues are FIRMWARE RELATED, because these firmwares aren't fully optimized, just generic RK3xxx roms.
Not good drivers at all...
And not all manyfacturers optimizes their own firmwares.
Produce and forget policy.
EQUANCY said:
hi,
Thanks for your best wishes, hoping same for you.
For the issue,
Possible answer for WiFi Direct function is Firmware related, because I didn't touched any system file except su binary and build.prop.
I also tested by my self, receiving files from TVBox is working but transfering to the device isn't via SuperBeam.
As I said before, I suppose it is a firmware bug and must be reported.
And question is:
To who
However, you may ask other users who is using another firmware versions or custom roms.
Happy new years...
Click to expand...
Click to collapse
I sent a email to cloudnetgo support, let's see what comes out (probably nothing...)
daviddema said:
I sent a email to cloudnetgo support, let's see what comes out (probably nothing...)
Click to expand...
Click to collapse
You've done very well my friend, please let us know if you get an answer from them.
EQUANCY said:
You've done very well my friend, please let us know if you get an answer from them.
Click to expand...
Click to collapse
I also tried to get screen mirroring to work with the wifidisplay app included in the ROM (is this also part of the original image or did you add it?).
Again, I can set up the mirroring connection between a Samsung Note 3 and the wifidisplay app, but then actual mirroring never happens. I suspect that whatever causes wifi direct not to work also causes the mirroring not to work... pity as this is would be a nice feature...
@EQUANCY,
I have a strange issue related to sound settings, its because of the stock firmware issue, hope you give some pointers on this
in the sound devices settings, there is input sound device and o/p sound device. I understand abt the output sound device, but what is the use of input sound device ? and is by default always set. Is there a way to disable the i/p device ?.
I ask this bcasue, my sound bar sony will cutoff the sound to other devices if the cs968 device is switched-off, if in on/standby mode, the sound passthorough (via cs968 )for other devices i hv connected to my soundbar. My guess is that since sound input device is checked(Radio button on), sound bar thinks that it has to pass through cs968. If i unplug the hmdi cable from cs968, the soundbar wrks fine.
My guess is that somewhere in the settings xml file, there shd be a way of disabling the sound input device.
I tried decompiling settings.apk and settingsprovider.apk searched all file with sound as filecontent key, but could not find anything related to disabling of sound input device.
can you help me on this ???
daviddema said:
I also tried to get screen mirroring to work with the wifidisplay app included in the ROM (is this also part of the original image or did you add it?).
Again, I can set up the mirroring connection between a Samsung Note 3 and the wifidisplay app, but then actual mirroring never happens. I suspect that whatever causes wifi direct not to work also causes the mirroring not to work... pity as this is would be a nice feature...
Click to expand...
Click to collapse
Wifi Display part of firmware self, I didn't add by myself and yes it is not working properly, I've read at somewhere this application supports only Nexus devices but I'm not sure.
hanu_blr said:
@EQUANCY,
I have a strange issue related to sound settings, its because of the stock firmware issue, hope you give some pointers on this
in the sound devices settings, there is input sound device and o/p sound device. I understand abt the output sound device, but what is the use of input sound device ? and is by default always set. Is there a way to disable the i/p device ?.
I ask this bcasue, my sound bar sony will cutoff the sound to other devices if the cs968 device is switched-off, if in on/standby mode, the sound passthorough (via cs968 )for other devices i hv connected to my soundbar. My guess is that since sound input device is checked(Radio button on), sound bar thinks that it has to pass through cs968. If i unplug the hmdi cable from cs968, the soundbar wrks fine.
My guess is that somewhere in the settings xml file, there shd be a way of disabling the sound input device.
I tried decompiling settings.apk and settingsprovider.apk searched all file with sound as filecontent key, but could not find anything related to disabling of sound input device.
can you help me on this ???
Click to expand...
Click to collapse
Disabling sound input?
As much as I know, the only sound input is internal microphone.
I real don't know the other sound inputs and als no clue about disabling it.
If you mean sound output such as Analog, Optical and HDMI then may be there is option but for input, I have no idea.
Sorry.
Uninstall Apps
How can I unistall app like bsplayer?
Thanks
Hi,
Open RootBrowser (usually opens in main directory) if not then got to Main Directory first then next to
\System\App
And long press the application which you want to remove and select Delete.
Or download a root uninstaller from market then uninstall what you want.
Hope this helps.
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Hello my magisk cannot seem to find the module you were referring to. Do you have another link where i can download the module?
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
thorvall said:
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
Click to expand...
Click to collapse
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
I worked.
Fillint said:
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
Click to expand...
Click to collapse
Thanks :good: . I actually did look at the thread before, but had the impression that the GSI Treble roms were of the ASOP variant, contrary to the note: 'NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.'
Am I wrong, or is it the note that does not apply in this case?
it looks like not both ways aren't working for 9.0 Havoc.
we need better solutions.
I tried these solutions on the Lenovo Z5 pro GT, but the Phone won't recognise any bluetooth IEM's. The sound keeps playing over the speaker. Does anyone have a solution?
When I change vendor to r/w it goes back to file system read only and I can't save the build.prop file afterwards
If someone was able to make it work can you please show me the build.prop permissions!!
this ROM is awesome. but there's a problem. my BT headphone no sound.
in developer options, "disable bluetooth A2DP hardware" can't be turned off. any solution?
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
kidronvalley said:
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
Click to expand...
Click to collapse
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
AllexBast said:
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
Click to expand...
Click to collapse
im gonna try this too because my Maxpad i10 plus as this issue
blaze2051 said:
im gonna try this too because my Maxpad i10 plus as this issue
Click to expand...
Click to collapse
Teclast M40 How to unlock bootloader?
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if...
forum.xda-developers.com
@AllexBast
by any chance have you experianced slow command response with ADB? I just install win10 1803 pro and its so so slow to even run adb devices command. does it make a difference if my device is running GSI Phh A11?
Did the trick for me! Thank you
SrCDA said:
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Click to expand...
Click to collapse
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
hd_scania said:
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
Click to expand...
Click to collapse
It can be done with root or in TWRP.
But now most phones have aptx-aptXHD support in original firmware, so there's a high possibility you don't need this step. By the way, it is not worth it to fix A2DP though, cause for now it's almost not possible (at lease I didn't solution) to fix bluetooth in call and A2DP offload at the same time. For me bluetooth in call is more important, and there's actually no side effect to turn off A2DP offload as far as I understand.
Anyways, to make bluetooth in call and Aptx (of course others like LDAC) both work, you'll need to:
1. remove /vendor/overlay/BluetoothResCommon.apk (if presented) (if presented and deleted, do a factory reset)
2. remove /vendor/etc/a2dp_audio_policy_configuration.xml
3. Enable "Force-disable A2DP offload" in phh settings
4. Enable "use alternate audio policy" in phh settings if your volume adjustment have any problems (if you got multi ones in different feature category, try different combination until it behave normally)(may require reboot)
5. flash Magisk module "aptx-HD-magisk-10_arm.arm64.zip" to fix aptx support
Now both sbc-aac-aptx-aptXHD-LDAC and bluetooth in call should work. Tested on 2 Qualcomm setups recently with phh android 12 based rom.
Hope this could help you and others having same issues.
XT19443 said:
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
Click to expand...
Click to collapse
Tho Xiaomi's MIUI really modified the whole aosp crazyly,but the device itself is still treble-compactible
the file is called MIUIbluetoothres.apk(probably,on miui 12.5's vendor)
BUT you dont need to del it.
To Fix: TURN ON "force disable a2dp offload" in phh treble settings.
that's it.(worked on redmi 10a.(MTK))
(ps: actually aptx is a qcom thing so it probably wont work on mtk devices.)