Details :
Nokia CK-15w Bluetooth Car Kit
Any HDCR Kernel Based ROM
It seems that any HDCR Kernel based rom causes the Nkia car-kit to reboot when downloading contacts.
I was originally running WildPuzzleRom v8.0.11 FRF91 2.2 (kernel 2.6.32.21-g4b3e397 htc-kernal) which worked as expected and I could download the contacts to my Car-Kit.
I them swapped to CM7 RC1 (great work by the way) and contact download starts, but then causes the carkit to reboot. I tried the nightlies for a while but same issue and then tried RC2 but same issue.
I have tried different versions of the Kernel 4, 4.1 and 4.2 but that all cause the car kit to reboot when downloading contacts. I have tried a second Nokia CK-15w Car Kit and the same problem occurs.
I put CM6 on the phone, but same problem and have since tried a few HDCR kernel based roms but they all have the same problem. So I can only think something in the kernel is causing the issue.
Bluetooth connectivity works well, but contact download is the issue.
I quite like CM7 and would be very happy if I could resolve this issue, but so far I have been unable to. I also posted on the CM forum but have had no response.
So thought (i am new to this) I would ask here if anyone has any ideas? or if there is a Stock (non hdcr) rom i could use with either cm6 or cm7?
There is a new kernel in the latest nightlies (nFinity tuxbox by Arco), and, you can check that out. But, remember, some people are having other issues with that, like 3G not working, call drops when screen shuts off etc. There are fixes available in the CM thread here that solves it,but you will have to hunt a bit.
Either way, a Nandroid backup before trying it is essential.
3xeno said:
There is a new kernel in the latest nightlies (nFinity tuxbox by Arco), and, you can check that out. But, remember, some people are having other issues with that, like 3G not working, call drops when screen shuts off etc. There are fixes available in the CM thread here that solves it,but you will have to hunt a bit.
Either way, a Nandroid backup before trying it is essential.
Click to expand...
Click to collapse
its actually just nfinity.
Tuxbox is the name of Arco's host computer
Cheers, just downloaded CM7 nightly 30 so will at least be able to check to see if the contact downloads works. If its all good then will have something to look forward to once the other issues are resolved. I always take a nandroid backup lol Better safe than sorry.
Hi all.
I have been waiting for the official Froyo update for G3 since last year August. I haven't tinkered with my phone at all and it is the stock 2.1 FW available by default in India (DDJG5).
However since the DDJP2 has been released, i have read forums with people having endless issues with this build. (Which is really disappointing from Samsung considering they made us wait so long).
So I have finally decided to flash froyo as i don't think Samsung will bother to provide a fix for the JP2.
And i wanted to know which stock ROM is the best, with least number of issues - JP2, JPF or JPM??
Also will i have any issues with network connectivity if i am flashing a ROM from a country other than India?
It would be great if we could also have a comparison of the custom ROMs available. (From what i have read so far Kyrillos seems the best IMO, but i am not too confident with flashing and partitioning as i have never done it before)
Well, you can only try for yourself. One thing is certain though, you can forget JPF. It's old and outdated.
I haven't tried JP2, but JPM in my opinion is the best froyo rom out there. Haven't had a single problem with it, and battery lasts very long. All major custom ROMs are based on JPM, too.
Thom47 said:
Well, you can only try for yourself. One thing is certain though, you can forget JPF. It's old and outdated.
I haven't tried JP2, but JPM in my opinion is the best froyo rom out there. Haven't had a single problem with it, and battery lasts very long. All major custom ROMs are based on JPM, too.
Click to expand...
Click to collapse
Thanks for the input.
I see you are using Kyrillos 4.1. Can i flash it over JPM if i consider a change later? Or do i have to flash JPF first and then Kyrillos? Also is it required to partition the sdcard for Kyrillos or can i just flash it and it will work fine?
yes you can flash it, and no, I don't think it's necessary to partition your sdcard
Thanks again. And one more question. I have seen a few versions of JPM floating around. Some with bootloaders, some without them, some say it is onepackage, etc etc. I don't really understand fully what they all mean by that, so could anyone point me to the latest JPM build, (with the least possibility of getting my phone bricked).
If it reads JPM then It's the latest build, always. There might be different ways to flash them (it can be a one package or in parts, as you said). So yeah doesn't matter, but if your JPM comes in parts, don't flash the bootloader. The only way to brick your phone during flashing is if you're flashing the bootloader and then lose USB connection for a reason or another.
As for partitioning sdcard.. I think you need to do it in Kyrillos. At least I did, as it showed me 0kb as internal memory. Kyrillos (and\or his thread?) can confirm this.
Oh and I cannot remember what ROM I flashed before flashing kyrillos, but I've seen the man himself suggesting people to flash JPF first if anything goes wrong or the phone doesn't boot. And I this was what I had to do to get Kyrillos' ROM to boot
I was using stock eclair 2.1 DDJG6 in India while other was flashing custom rom all around. I had a facination with live wallpapers so i rooted my phone and used it. Then i got offcial update directly from kies. Probably the first one in India. After checking it out i figured several bugs such as the youtube,camera,music player,stock browser. So i was wondering to take a risk and flash my phone confused betwwen JPM Stock and Krillos 4.1. Then i plucked up the courage an then flashed it with non overclocked version without partitioning my card directly from DDJP2 to krillos 4.1. Its pretty good atleast better than so called OFFICIAL FROYO DDJP2 we were all eagerly waiting for. **** YOU SAMSUNG.
Just saw on Samfirmware.com:
Europe releases XWJPE(March 30) and XWJPF(April 5) are they improvements on the XXJPM (Feb)...
It would be great to have all the issues and advantages of the latest FW in a tabulated format won't it? Would sure help a lot of people in deciding.
@ayan - How is the Kyrillos working out for you?, facing any issues in usage? Just flashed it using Odin with the tar file and the ops file?
I haven't tested these new roms out, but they most likely wouldn't release 'em if there was no improvements.
Oh and XXJPF is the outdated one I was talking about, this ROM is XWJPF, which as you said, is newer then JPM.
thanks
thanks Nice idea !!! ^^
android_murphy said:
Just saw on Samfirmware.com:
Europe releases XWJPE(March 30) and XWJPF(April 5) are they improvements on the XXJPM (Feb)...
It would be great to have all the issues and advantages of the latest FW in a tabulated format won't it? Would sure help a lot of people in deciding.
@ayan - How is the Kyrillos working out for you?, facing any issues in usage? Just flashed it using Odin with the tar file and the ops file?
Click to expand...
Click to collapse
Yes i just thought its better to do that way. And as off now Kyrillos is good. But the camera bug is still there. I dont know. I am thinking to trying the new firmware XWJPF . Lets c how it works.
I just flashed JPM build from samfirmware.com and it is root by default. Some issues i am having:
1. GO Launcher Ex keeps restarting 90% of the time i hit the home button.
2. Not able to log into facebook and twitter account sync, however facebook and twitter individual apps are working.
3. The sizes of most apps in the App Management list is shown to be below or around 1mb.
4. GPS signal not locking on.
If anyone else is also having these issues or can remedy them please tell me.
android_murphy said:
I just flashed JPM build from samfirmware.com and it is root by default. Some issues i am having:
1. GO Launcher Ex keeps restarting 90% of the time i hit the home button.
2. Not able to log into facebook and twitter account sync, however facebook and twitter individual apps are working.
3. The sizes of most apps in the App Management list is shown to be below or around 1mb.
4. GPS signal not locking on.
If anyone else is also having these issues or can remedy them please tell me.
Click to expand...
Click to collapse
Srry atleast i dont know about it. Try the new europe version its better than JPM i think. And do you have the link of it ?
android_murphy said:
I just flashed JPM build from samfirmware.com and it is root by default. Some issues i am having:
1. GO Launcher Ex keeps restarting 90% of the time i hit the home button.
2. Not able to log into facebook and twitter account sync, however facebook and twitter individual apps are working.
3. The sizes of most apps in the App Management list is shown to be below or around 1mb.
4. GPS signal not locking on.
If anyone else is also having these issues or can remedy them please tell me.
Click to expand...
Click to collapse
Problems 1,2,4 resolved after a few restarts. No. 3 still persists (although one can easily live without a fix for this ).
Really love the JPM rom... No real issues as of yet ...
I also have that app size thing and think it as a bug that I can live with.. it also exists in other ROMs. My theory is that the system has moved it to external storage and for some reason reading it as if it was installed on internal storage, and reads that it takes 0mb of phone's memory. I could be wrong, though.
Hope that wasn't too messy explanation
One bug i noticed just now ... Wifi takes too long to switch on and most of the times gives error. Only switches on after 3-4 continuous tries. Is anyone else experiencing the same??
This also makes me ask a question, can my G3 work on a wifi created by my laptop? if so, then how? Because i have an internet connection through a lan cable, and would like to utilise it on the phone to save up on the 3G data charges.
I like JPM IT is stable
hi,
i tried many ROMs on my ZTE BLADE V2 yoigo (ES) and all had this problem, including the stock one.
When using Viber or MobileVOIP the sound would go to the external speaker and not the internal one!!
I only use the phone to make VOIP calls and internet so this is a big issue.
The problem was long discussed over the cyanogen, code.google.com/p/cyanogenmod/issues/detail?id=2858
One guy, at #55 offers a libaudio.so which appears to fix this problem. Can it be inserted on this rom??? (which from all other tested, stock, cyanogen 7.2 kang this one appears to have the longest battery life)
thanks for any advice.
PS:
1. I tried the trick with opening the Radio App and closing it, does not work with this rom
2. I tried overwriting the libaudio.so inside the zip, copied the rom to the phone and installing it but it fails saying bad zip,something like this..
3. anyone can confirm a ROM version for ZTE that has this problem fixed?
CyanogenMod has this problem fixed, it's not easily possible to fix it on ZTE roms. You'd need to compile your own fixed libaudio.so a CM7 one wont work due to it being compiled for vmsplit3g & other cm7 modifications.
You can use the native gingerbread sip/voip calling feature in ZTE Gingerbread roms, as long as you're using a cm7 or aosp contacts/dialler rather than the zte version, that works ok, it's just 3rd party apps.
I have ported greeneyes's sense 4.1 rom (http://forum.xda-developers.com/showthread.php?t=1980122) and i will upload the rom, make thread etc in friday because of my slow internet connection.
Currently not working: Wifi (shows error-because of the kernel), Bluetooth (turns on, but wont discover any devices), Camera (stock camera-no, should work with 3rd party apps but i didnt test it), 3g (should also work, but can't add apns-says that sim card is not inserted), there are also a few bugs here and there but nothing big. Everything else works perfectly and the rom is very smooth and stable.
The real problem and the reason i made this thread is because of the kernel i used for this rom, which is outdated aka shakys kernel from his rom (sense 4.0) ...and not the greeneyes's because i dont know how to port kernels, actually i know very little about kernels. Anyway if it werent for shakys kernel i wouldnt be able to port this rom, @shaky thanks.
So if anyone is interested in this rom he could help with kernel and these bugs, any tips and suggestions are welcome!
Hi all,
I noticed that the Google Edition Roms are starting to trickle in (Pulled from the Google Editions of our phone). Will we be able to flash it on our AT&T devices?
This will definitely make me flash instead of sticking with TW now. The Verge is reporting that they got a 3rd party remote app to work with their Google Edition S4!
Death&co said:
Hi all,
I noticed that the Google Edition Roms are starting to trickle in (Pulled from the Google Editions of our phone). Will we be able to flash it on our AT&T devices?
This will definitely make me flash instead of sticking with TW now. The Verge is reporting that they got a 3rd party remote app to work with their Google Edition S4!
Click to expand...
Click to collapse
Yes you should, just be sure to flash the att kernel and superuser zip before exiting recovery. Also, double check, but I've read you need the touchwiz version of our kernel not the aosp version which seems odd to me. From the reports I've read though, the google edition rom is very much a work iin progress. It's probably better to just wait a few days for the major s4 rom developers to incorporate the goodies into their roms.
I used the ROM that's going around for the i377m does not flash the Modem so those are both stock and the ROM runs perfectly from what i can tell so far (only been a few hours, still need to test LTE properly).
I think that the touchwize framework is still integrated deep in the ROM, it's just all the top level stuff has been removed. I've even heard reports of the touchwize camera, dialer and such working on the google edition.
Edit:
The ROM does flash the kernel, I'm using the [email protected] kernel and the phone is functioning properly.