Related
Hello,
I've been reading this forum for quite some years and using some of the tutorials and ROMs from here but never actually posted anything and now that I have a few questions about on of the ROMs I'm using now I'm not quite sure where to post it since as a newly registered member I can't post anything in the correct ROM Thread [ http://forum.xda-developers.com/showthread.php?t=2467013 ], so please be patient with me.
I thought it would make more sense to post my actually questions than trying to reach those 10 posts to be able to post it directly there.
So now to my questions:
I have a HTC Desire S (obviously) and had for about 1 1/2 years now an old CoreDroid Version from here (can't remember which one) which I was quite happy with till it started to crash more and more often, battery kept draining and then there came a point a few weeks ago where it would just randomly go out and wouldn't restart till you charged it again.
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
The next thing is still a worry to me, I used to sync my contacts from my outlook through android-sync [ http://www.android-sync.com/ ] which I bought after non of the other syncing methods worked to my satisfaction. Everything worked fine with the old ROM (after I set it up) but with the new ROM the program on my computer can't find the mobile phone anymore, I tried to reinstall the ADB drivers, but it didn't work (I sent the error log from the program to the developer a few days ago but still haven't heard back), so maybe someone around here knows a way around it?
Last night I experienced another issue, the clock works fine and after I installed the ROM I set up a few different alarm clocks and they worked. But yesterday I wanted to change the alarms and now every time I try to access the alarm clock the clock app stops working "Clock stopped working" and it closes.
I can delete the alarms and set up a new one, but only the time, then it saves and when I try to change the days or the sound same error appears. I searched the forum and internet for a bit and found ideas like deleting the clock data and cache, rebooting the device, but none worked.
And last but not least it seems I can't find the right settings for it but every time I swype or type on the keyboard it vibrates. I turned off all the other noises that the phone made while typing but this one I can't find. I would like my phone to be silent and don't vibrate when I type. Where can I find the settings for it?
If anybody could help me with this I would appreciate it a lot.
Kind Regards
Marvin
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
SKENER said:
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
Click to expand...
Click to collapse
I installed Flinny alpha 5 CM11 now and tried it out. I had a few crashes with the devil-kin version too and bought a new battery, so hard to tell what solved what, but so far so good.
But for the syncing problem, now I have an even worse error:
ht*p :// i.gyazo.com/798a67697deb9f91904e7cac9b62bf76.png
with the devil-kin version it still found something and just had problems with the adb drivers, now there seems to be something else going on.
m4rvin88 said:
Hello,
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
Click to expand...
Click to collapse
Regarding that issue I also got problems with many other apps i.e. Redphone, Textsecure, Chiffry and so on there always comes the message that these apps are incompatible to my device - strange I also use cm11_saga_flinny_alpha5 Kernel 4.4.2.
These messages of incompatibility are generated by Google play store, when comparing AndroidManifest.XML permissions and requirements with the phone...
Further more Issues at Finny/Devilkin CM11.0
Hello guys,
I am also new at this Forum although using it "passiv" since years. Now I flashed the CM 11.0 from Devilkin and ones from Flinny.
- Unofficial CM10.2 / CM11.0 build for Saga / Desire S
All works (both ROMs) great up to the wired headphone Controles.
I think this might be the right thread to Post that until I reached the Number of Posts to put the in the right developerthread. Hope anyone can help.
The exactly problem:
I use orginal HTC-Headset with three controller Buttoms. The headphone itself is working though I can hear music and sound but the Controls and the Mic are not working. I tried to register an input with the jayzheadphone app but it shows no input. Headphone and controls worked fine with stock ROM.
Thank you for help.
@Terodax
Sorry but I cant't evaluate your issue cause of the missing HTC-Headset, but I got some other weird thing with the "mute" button on calling someboy it fails in doing it .-/
So I worked around the little problem in "holding" the call -> that works and it's like muting
htc wihc room to use
Hello
I bought this item.
http://www.ebay.com/itm/121361166744...84.m1423.l2649
Wich rom to android 4 or last?
How can I install those rom?
I need to using zip flashable file on recovery mod or addoin way?
will I need to flash the modem (phone) after?
has the recovery a nandroid backup option? I wanna backup the current rom like it is.
which is the best recovery for that item?
Thanks
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Hello
I need to use whatsapp and facebook mensseger on it.
thanks
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
seems like noone has this kind of troubles
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
loth77 said:
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
Click to expand...
Click to collapse
geri.st said:
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
Click to expand...
Click to collapse
loth77 said:
seems like noone has this kind of troubles
Click to expand...
Click to collapse
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
J0ch3nK said:
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
Click to expand...
Click to collapse
https://jira.cyanogenmod.org/browse/BACON-2822
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
this is still CM and not oxygen OS
Bluetooth isn't working on any ROM with any kernel combination! Not even the default kernel that comes up with the ROM. I'm talking about bluetooth file transfers, not connecting to speakers or anything. When I transfer/receive a file, it says 'Unfortunately com.android.bluetooth has stopped.' and then bluetooth is stuck on 'Turning on bluetooth...'. After rebooting, the bluetooth is already ON but still the same thing happens again when I use it. I can just connect and pair devices, can't share any file with them. Tried clearing data and cache of the Bluetooth Share app too, nothing helped.
It's strange because it works perfectly on OxygenOS with any kernel flashed on top of it. It's just perfect with Oxygen... ONLY! On all CM (never tried CM12S or COS12.1, I'm talking about CM12.1 only because I'm not gonna use others at all!) , Slim and other ROMs, the same problem occurs with all the kernels.
I thought the problem wouldn't be somewhere in the /system or /boot partitions and so I tried flashing OxygenOS and a CM12.1 ROM on top of it without booting into OxygenOS. Still, bluetooth doesn't work.
Help! I don't know where I'm wrong but I know that this is just happening with me and no other OPO user!
See the attachment for more information.
Got the culprit. Don't flash the Xperia Z2 Smart Social Camera on OnePlus One. I found it here . It breaks the bluetooth on any ROM. And on OxygenOS, the ROM will keep on saying 'Camera has stopped.' , so I didn't flash it.
Hello, and welcome to a short and sweet guide on the way I have found to successfully root our device, the blu studio energy 2!
DISCLAIMER - I am not a developer, and any knowledge I have has come from reading forums and tinkering with android devices I have owned. If you are reading this, you should know that I do not guarantee these steps will work for you, and will not be responsible for any damage this causes your device.
THINGS YOU WILL NEED
1. MTK VCOM Drivers Installed (Guide on XDA)
2. SP Flash Tool
3. Scatter file (modified from Gionee M4 version to match our partition table, attached)
4. TWRP Recovery ported to M4 by Hanuma50
5. SuperSU Flashable ZIP
PROCEDURE
1. Open SPFT, and load the modified scatter file
2. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded​3. Double click in 'Location' field next to recovery partition(screenshot highlighted in blue), and select Gionee M4 TWRP recovery.img
4. Click "Download" Button
5. Download/Copy SuperSU zip to phone
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Install SuperSU zip from TWRP
11. Reboot into system, you are now successfully rooted and with custom recovery!
From this point on, you can install any app needing root, and also perform full nandroid backups using TWRP on Blu Studio Energy 2.
TECHNICAL INFO
For anyone interested in what I have done, it is all very simple, and any credit should go to Hanuma50 at Needrom for porting TWRP to Gionee M4!
The reason we can use Gionee roms/recoveries on our device is because Blu devices are just rebranded (usually Gionee) phones sold in the US. So, all that I have done is use SP Flash tools to load an M4 recovery on our device!
The only real change needed was to change the scatter file, because apparently Gionee uses some different partition sizes than Blu does. Don't worry though, the recovery partitions are exactly the same, and the scatter changes are only to avoid errors that show up without them.
I changed the scatter to reflect the partition sizes/locations found in /proc/partinfo on our Blu phones. This is very easy and if someone is getting 'PMT changed' error in SPFT trying to do this on another MT6735 device, try changing the scatter hex values to match your partinfo file :fingers-crossed:
Just followed your instructions and seems to be working flawlessly!
I didn't have to first flash the drivers because I had already done that previously. When you connect the blu studio energy 2 to your computer via usb, it popus up with a cd of the drivers which you can install.
Thank you! This will make this phone so much better. Also, I must have been using an old version of twrp, because this version has a beautiful UI!
Any suggestions for programs to free or remove, now that we have root access? I am looking forward to messing with this phone now.
I tried installing xposed but was unsuccessful. Have you tried this? Thanks again.
Glad it worked out!
Have just been starting to mess with I thyself to be honest, I actually have gotten xposed to install, haven't gotten gravity box working yet. I installed xposed arm-64 sdk 21.
On a friend's phone I have flashed gionee m4 stock rom, which works really well and seems nicer in some respects to the Blu stock, but I am hesitant to flash it since I haven't found a foolproof way to backup the stock before flashing.
EDIT - I actually got gravity box working, using sdk21 arm64 xposed installer. Everything works really well surprisingly I've had more luck than on my old nexus 4 running stock 5.1. Everything works fine for me, except for power menu, and i think that's just about it for everything else I've tried. QS remapping and navigation button remappiny works great, hope it works for you too!
Outer then that, I have installed adaway and some other apps needing root and they work well. Hopefully we can start getting some nice development for this phone or the m4 in the near future!
danageis said:
Glad it worked out!
Have just been starting to mess with I thyself to be honest, I actually have gotten xposed to install, haven't gotten gravity box working yet. I installed xposed arm-64 sdk 21.
On a friend's phone I have flashed gionee m4 stock rom, which works really well and seems nicer in some respects to the Blu stock, but I am hesitant to flash it since I haven't found a foolproof way to backup the stock before flashing.
EDIT - I actually got gravity box working, using sdk21 arm64 xposed installer. Everything works really well surprisingly I've had more luck than on my old nexus 4 running stock 5.1. Everything works fine for me, except for power menu, and i think that's just about it for everything else I've tried. QS remapping and navigation button remappiny works great, hope it works for you too!
Outer then that, I have installed adaway and some other apps needing root and they work well. Hopefully we can start getting some nice development for this phone or the m4 in the near future!
Click to expand...
Click to collapse
Thanks, I thought I tried that version of the installer but I guess not. I'll give it another shot. Can't wait to see what kind of further dev work we get!
I flashed the 78 sdk21 64 zip for xposed but when I reboot it says optimizing apps and then reboots.
Any idea what I might be doing wrong?
portezbie said:
I flashed the 78 sdk21 64 zip for xposed but when I reboot it says optimizing apps and then reboots.
Any idea what I might be doing wrong?
Click to expand...
Click to collapse
Mine did that too, you have to let it do it's thing. It will say optimizing, and keep rebooting, but after every reboot it SHOULD have 1 or 2 fewer apps listed that it says its optimizing. Pretty weird, but afterward it does seem to have installed correctly. It took my phone about 25 minutes of the rebooting, but afterwards I haven't noticed any issues with xposed/gravity box LP.
danageis said:
Mine did that too, you have to let it do it's thing. It will say optimizing, and keep rebooting, but after every reboot it SHOULD have 1 or 2 fewer apps listed that it says its optimizing. Pretty weird, but afterward it does seem to have installed correctly. It took my phone about 25 minutes of the rebooting, but afterwards I haven't noticed any issues with xposed/gravity box LP.
Click to expand...
Click to collapse
Oh weird. Thanks for the explanation!
Just curious, have you had any trouble playing music on your phone? I have problems playing through aux and Bluetooth.
danageis said:
Just curious, have you had any trouble playing music on your phone? I have problems playing through aux and Bluetooth.
Click to expand...
Click to collapse
What kind of problems are you having? I've only used my energy 2 with headphones and once briefly with a bluetooth speaker just to test it. I've had no trouble with headphones and my brief test with bluetooth audio seemed fine.
If you tell me what problems you're having I can try and test it.
portezbie said:
What kind of problems are you having? I've only used my energy 2 with headphones and once briefly with a bluetooth speaker just to test it. I've had no trouble with headphones and my brief test with bluetooth audio seemed fine.
If you tell me what problems you're having I can try and test it.
Click to expand...
Click to collapse
Ok thanks!
The problem I'm having with aux connection is that the phone thinks the connection is lost/reconnected every few seconds. So after a while, the music will either keep pausing itself, or cut out every few seconds. I have only had this problem with aux cables into stereos, but I have tried multiple cables with the results.
With Bluetooth, there are stutters in the audio.
I have actually returned the first phone I got to amazon because of this problem, and the second one did the same thing, but maybe I really did just get two duds in a row?
Thanks for your help!
danageis said:
Ok thanks!
The problem I'm having with aux connection is that the phone thinks the connection is lost/reconnected every few seconds. So after a while, the music will either keep pausing itself, or cut out every few seconds. I have only had this problem with aux cables into stereos, but I have tried multiple cables with the results.
With Bluetooth, there are stutters in the audio.
I have actually returned the first phone I got to amazon because of this problem, and the second one did the same thing, but maybe I really did just get two duds in a row?
Thanks for your help!
Click to expand...
Click to collapse
So I just used the bluetooth speaker in my shower for 20 minutes to listen to pandora. I did not notice any stuttering. I will try hooking up the phone to my stereo tomorrow and seeing what happens.
portezbie said:
So I just used the bluetooth speaker in my shower for 20 minutes to listen to pandora. I did not notice any stuttering. I will try hooking up the phone to my stereo tomorrow and seeing what happens.
Click to expand...
Click to collapse
Hmmm, weird... well thanks for your help!
danageis said:
Hmmm, weird... well thanks for your help!
Click to expand...
Click to collapse
Connected it to my stereo with a standard 3.5mm cable and listened to a podcast with pocketcast. Didn't experience any problems.
portezbie said:
Connected it to my stereo with a standard 3.5mm cable and listened to a podcast with pocketcast. Didn't experience any problems.
Click to expand...
Click to collapse
Hmm... Well, thanks for checking. I'm not sure why I'm having so many problems...
danageis said:
Hmm... Well, thanks for checking. I'm not sure why I'm having so many problems...
Click to expand...
Click to collapse
I'm trying to think what could be different. I haven't installed xposed on my phone, maybe it is something related to that, or some other change that you have made and I haven't?
portezbie said:
I'm trying to think what could be different. I haven't installed xposed on my phone, maybe it is something related to that, or some other change that you have made and I haven't?
Click to expand...
Click to collapse
I'm not sure, I have tried it out with the same problems on both phones, right after I got them from Amazon, before I made any changes
danageis said:
I'm not sure, I have tried it out with the same problems on both phones, right after I got them from Amazon, before I made any changes
Click to expand...
Click to collapse
Crazy. I have no idea then.
I received this phone yesterday and have been playing around with it. My previous phone was a Samsung Blaze 4G (yes, really old but still chugging along) that was rooted and running Cyanogenmod 10. I am planning on rooting this phone, but was curious if anyone had tried using Kingoroot to do so?
Apologies if this doesn't belong in this thread, I was just curious about the various methods of rooting that might be available.
Cheers!
Update: Kangoroot does not currently root the Blu Studio Energy 2 phone (sorry, I was impatient). I will have a crack at it using your method listed by the OP.
Vinotas said:
Update: Kangoroot does not currently root the Blu Studio Energy 2 phone (sorry, I was impatient). I will have a crack at it using your method listed by the OP.
Click to expand...
Click to collapse
I have tried all the one click root methods I could find and none of them worked. Just use the ops method, it is quite easy and works like a charm.
On an unrelated subject, I tried installing xposed and after reading ops description it worked fine for me. Have had no issues since installing xposed although gravitybox didn't seem to work properly, but I think that is due to the phone's rom. Amplify works great and so does greenify. I am currently testing out powernap, and it seems to work so far.
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
roytje88 said:
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
Click to expand...
Click to collapse
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Youdoofus said:
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Click to expand...
Click to collapse
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
roytje88 said:
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
Click to expand...
Click to collapse
yeah, reflash the same ROM or try a different one. Back in the day, there were tons of issues with stuff that was designed to work on the phone based on specific kernel programming that spoke to the hardware to allow these features to physically operate, but only in touchwiz based ROMs, AOSP based ROMs were left out in the cold. With the emergence of the necessity of a clean knox in order for certain things to work, i have given up on root for the time being so that i can enjoy the awesomeness that is paying for stuff with my watch (which requires an unrooted phone to work. Technically your phone can be rooted but it makes it a pain in the anus)
anyways, i think your audio issue might be a GSI specific thing, just a hunch tho. Might want to go look in the GSI threads and see if there is a list of what works/whats broke in the ROMs. They usually just come out and tell you if ti doesnt work because if its the other way around, the devs reputation will be tarnished
I flashed Lineage OS 16 (Android 9) GSI. Same problem. Also with other Bluetooth devices. I'm thinking it's the vendor I flashed. I did find an Oreo vendor for this device mentioning Bluetooth calls don't work.
Searched for a rom without Treble but couldn't find one that has December security (or November). For now I'll use my earbuds when calling from the car.
I could flash a number of images, but don't really want to the time of finding the perfect rom for my devices has passed. I'll just keep this rom and when I feel like it, I'll flash the stock rom.
Thanks anyways for the advice!