hi everyone.
I'm from argentina and I have a problem with notifications using any android 4.x ROM, the only one which has worked for me was SexyNogenMOD based on Android 4.1.2 and kernel QWERTY 2.6.3. notifications work well only using the program Wake My Android Pro, otherwise I couldn't figure out the combination for this to work well.
I'm actually using Vurrut 2.3 KPU ROM, which works great! (using Wake My Droid program), but sometimes I want to install programs that only work on android 4+ and well, I cannot.
My phone is I9003L and using EFS files from my distribution ROM.
Does anyone experimented issues like this? or does any know how can I solve this? using any other android notifications are always late
Related
Hy,I would like to know more about the android versions and custom roms.
1)Why some devices do not support new versions of Android?
Why is not working as a PC operating system? For example when windows7 appeared most of the PCs could install windows 7.
2) Why is possible using a custom rom like cyanogen to update to a newer version of android although this version is not released by the producer. Ex. install ics on galaxy S.
3) Using a custom ROM can update a device from the first version of Android to the latest one?
Thank you for your help.
Catalin
To answer your questions as best I can...
1. Most phones can support almost any version of android. It all has to do with their chipset.
2. When a custom ROM is created, it is based on a certain version of the OS. It is custom because it is modded by developers to be compatible with different devices.
3. Yes. This is true depending on, again, the device and the developers. For me, I have had many devices that were on froyo 2.2. And would not get an OTA update. Whereas a custom ROM could kick it up to gingerbread 2.3 or ice cream sandwich 4.0.
I hope this helps!
Sent from my HTC Vision using xda premium
1. the problem is with your carrier or manufacturer usually. some push updates through fast, others test updates before letting users update. also older phones get forgotten. a new phone will be more likely to get updated than an old one. they want you to buy a new one
2 and 3 what i337 said. i would just add that using a rom bypasses the problem in #1
Also one of the big issues are the drivers. The open source drivers work but don't use the hardware to the fullest. Also non of the OEM related apps and stuff work on AOSP roms. Then you have app compatibility issues with AOSP roms as well.
I am getting the itch to put on a custom ROM of my GS3, but I have a Fitbit One and would like for it to continue to update over the phone. I've tried CM10.1, but it appears that there is a problem with the BT4.0 and the phone doesn't want to try to connect to the fitbit. I'm not close to a computer much currently to update the fitbit.
TL: DR- Is there a working ROM where the BT4.0/BLE is working somewhat properly?
Thanks in advance.
I'm looking for the same thing. I switched back to a Stock variant to get BT4 working and the Stock ROM is total garbage after using Cyanogen Mod. I don't want to have to choose one or the other!
There is not a single ROM out there at the moment that has Bluetooth 4.0 working. Google has not released or included a lib file for it to work. Sure our devices have the hardware but the software has no clue how to utilize it. Maybe next version of android will have it.
The 4.1.2 Omega ROM was working for me. The ROM will need to be based off of Samsung's official as it will need their hacked Bluetooth stack - they worked directly wth Fitbit to get it up and running. I've since upgraded to the Omega 4.2.2 AOKP ROM and it no longer works (which I expected).
BLE
The only ROM that i've found with working BT4/BLE is the one by beanstown.. i do confirm it working just fine for my fitbit flex.
http://forum.xda-developers.com/showthread.php?t=1973982
I have a fitbit as well and I am trying to figure out what it would take to get it working with CyanogenMod. I flashed an unofficial 10.2 (4.3) and still no luck with the fitbit.
try the 4.3 version of CM in teh development section? I thought this was an added or fixed feature in teh newest version of android. not too sure though.
I have installed couple of ROMs with old and new base-band ,ginger based , ICS bases and JB based and all ended with viber crashing while talking and my device stays unresponsive for like 10 minutes the only way to get viber working is by using the stock firmware with old base-band foryo based
how can i fix that?because stock ROM sucks and a lot laggy when compared to CM7 which im trying to use here
try stock 2.3.3
HTC Venom said:
I have installed couple of ROMs with old and new base-band ,ginger based , ICS bases and JB based and all ended with viber crashing while talking and my device stays unresponsive for like 10 minutes the only way to get viber working is by using the stock firmware with old base-band foryo based
how can i fix that?because stock ROM sucks and a lot laggy when compared to CM7 which im trying to use here
Click to expand...
Click to collapse
i am having the exact same problem while using viber with any custom rom......it used to work like a charm with stock 2.3.3 though
HTC Venom said:
I have installed couple of ROMs with old and new base-band ,ginger based , ICS bases and JB based and all ended with viber crashing while talking and my device stays unresponsive for like 10 minutes the only way to get viber working is by using the stock firmware with old base-band foryo based
how can i fix that?because stock ROM sucks and a lot laggy when compared to CM7 which im trying to use here
Click to expand...
Click to collapse
rinkuverma123 said:
i am having the exact same problem while using viber with any custom rom......it used to work like a charm with stock 2.3.3 though
Click to expand...
Click to collapse
But for it worked well with some nightly of CM7 (I can't remember the exact version). May be you can try a few and check if it works for you too.
Hi guys,
This is Viber's rep, I'm here to assist.
@HTC Venom - Unfortunately Viber is not fully compatible with custom ROMs. :/
Do you have the latest Viber version (2.3.6)?
Regards,
Viber
HTC Venom said:
I have installed couple of ROMs with old and new base-band ,ginger based , ICS bases and JB based and all ended with viber crashing while talking and my device stays unresponsive for like 10 minutes the only way to get viber working is by using the stock firmware with old base-band foryo based
how can i fix that?because stock ROM sucks and a lot laggy when compared to CM7 which im trying to use here
Click to expand...
Click to collapse
works on oxygen gb and cm 7 give it a try
Thanks all
Thanks all for answering ,
P500 is a really nice device to hold , i having at this moment more fun with though I also have HTC One X, so since my mom is using this P500 for viber purposes I have bought for her a Motorola XT311 which is a great budget phone and I took the P500 for me for ROM flashing , and for my use Im using viber on my HTC device like a charm , when it comes to viber we really use it like 3-4 hours a day, really
Viber Team said:
Hi guys,
This is Viber's rep, I'm here to assist.
@HTC Venom - Unfortunately Viber is not fully compatible with custom ROMs. :/
Do you have the latest Viber version (2.3.6)?
Regards,
Viber
Click to expand...
Click to collapse
I always keep it up to date , though its nots a rom specific , but I managed to run it great with stock RomS
Bonjour,
I use a i.t.works bluetooth keyboard with my Galaxy Mega 6.3
I used the 'azerty_keymap.zip' method described on the site.
I just install CyanogenMod 11 4.4 Kitkat and the method don't work anymore.
The Menu and Back buttons doesn't work and the bluetooth keyboard no more.
I have got to re-instal CyanogenMod 11.
Somebody knows this problem ?
Thanks.
Of course, I'm french!
Netcar1 said:
Bonjour,
I use a i.t.works bluetooth keyboard with my Galaxy Mega 6.3
I used the 'azerty_keymap.zip' method described on the site.
I just install CyanogenMod 11 4.4 Kitkat and the method don't work anymore.
The Menu and Back buttons doesn't work and the bluetooth keyboard no more.
I have got to re-instal CyanogenMod 11.
Somebody knows this problem ?
Thanks.
Of course, I'm french!
Click to expand...
Click to collapse
BUT i will also help you try to help...
Have you just tried change keylayout within the rom? You don't need a zip for it i suppose Additionally:
Which rom was installed before? have you performed a full wipe or just updated? Have you tried if bluetooth itself works properly? And tried another keyboard app? TouchPal X is simply LEADING
I use this method :
http://forum.xda-developers.com/showthread.php?t=1082408
since 2 years with Cyanogen 9, 10..
It works on my Note2 with Paranoid Android 4.2.2.
Netcar1 said:
I use this method :
http://forum.xda-developers.com/showthread.php?t=1082408
since 2 years with Cyanogen 9, 10..
It works on my Note2 with Paranoid Android 4.2.2.
Click to expand...
Click to collapse
Time to try something new. Wonder it worked with all these different roms. :=)
Hhi, idk if this is right forum but ya this is my question and please answer me.
so, i have my old mtk6582 phone based on jelly bean. (also it is my first ever phone i got)
always since childhood i am trying to have it upgraded to al least android 4.4.4 (kitkat) but i also know it is not possible because it would require an upgraded kernel.
i manage to find similar phone with similar specs but problem is phone boots up and but touchscreen doesn't work and require to be used using mouse.
so my question is, is there any ways to make or porte kernel for aosp based stock ROM (android one) phone.
if method is for Linux (ubuntu) system it would be grate. thanks for help.