Related
I'm looking to try out an android build. Can someone recommend a build to use that's easy to set up. I need data, and gps to work. Also would I be able to flash back to WM if I don't like the build?
Not sure of an Android build to meet your needs, though I would like it too!
To flash back to WM is easy once I did a lot of reading. Just power your phone off, then turn power on with the camera button depressed too. This brings up the bootloader screen, then just flash your favourite WM ROM.
ski21 said:
I'm looking to try out an android build. Can someone recommend a build to use that's easy to set up. I need data, and gps to work. Also would I be able to flash back to WM if I don't like the build?
Click to expand...
Click to collapse
Hi ski21,
I was in your shoes just a few weeks ago. I now have a great Android build running on my Touch (Bell Mobility). Everything works and it “feels” like a native build like it was meant for this device.
With any of the Android builds you can always flash back to Windows Mobile. You just need to make sure you have an up-to-date (ie. GPS enabled) Windows Mobile ROM to return to. I am with Bell and use the most recent official Bell update so I can go back to a “supported” configuration.
If you have never flashed a custom Windows ROM before then you will need to install the “HardSPL” provided by ImCoKeMaN. This is an alternate boot loader that allows you to flash unsigned (non-official) ROMs. This is really the key to doing anything cool with your Vogue. Without this you can only every install an official ROM released by your carrier. I recommend version 2.31. If you have installed a custom Windows ROM before then you have already done this. You can find the information on this over at PPCGeeks in the link below:
http://forum.ppcgeeks.com/showthread.php?t=20370
Once you have the CoKe SPL 2.31 installed you will be able to flash any custom ROMs including Android builds. Flashing Android is a little different then flashing Windows ROMs. You will need a bunch of files:
First things first, you will need a copy of the ROMUpdateUtility. This is a Windows program that you use for flashing your Vogue. You can get this here:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Download and unpack this into a folder called ROMUpdateUtility.
Next you will need a Linux kernel with a screen size (resolution) appropriate for your device. This is the one I am using and it works great in conjunction with the ROM I am going to suggest next.
http://it029000.massey.ac.nz/vogue/files/voguimg-240x320-17-12-09.nbh
Download this file, copy it to the folder you unpacked the ROMUpdateUtility in. Rename it to RUU_signed.nbh.
Next you will need to download some “base files” as well as a system image (which is the main ROM). You copy these files to the SD card on the Vogue. You can get the “base files” here:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
You will then need to select your favorite Android build. I am using plemen's “Eclair themed” build. You can get this here:
http://forum.xda-developers.com/showthread.php?t=591104
Rename the system file you download to system.sqsh when you copy it to your SD card. Also download the data.img file and place it on your SD card (should be provided in the thread that you get the build itself from). In the “end” (just before you flash) you should have the following files sitting in the root of your SD card:
datafstonand
rootfstonand
systemfstonand
rootfs.img
data.img
system.sqsh (or system.img depending on the build you download)
Then you put your Vogue into boot loader mode. You do this by holding down the power & camera buttons and pressing the reset button with the stylus. Then run the ROMUpdateUtility.exe from your ROMUpdateUtility folder.
That just about covers it I think. I am a little unclear what all these different parts do but this should get Android 1.6 (if you download plemen's build) up and running on your Vogue. Enjoy.
Best regards,
The Fish
Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.
krwilson said:
Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.
Click to expand...
Click to collapse
that's normal
Well if it's normal then there's a problem. It will not let me connect, shows 2 bars, but says I have no network so I cannot connect to Google. If thefish123 is connected on Bell then I must have something wrong. I followed the directions exactly, but was somewhat unsure over the rootfs.img file for it is not too specific in the directions??? Anyway, flashed back again to NSFans. I have had another Android working but could not get tethering working correctly, I was hoping this one might do it. Using PDnet it just wouldn't work for me.
Also, sorry ski21, wasn't my intention to hijack your thread.
krwilson said:
Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.
Click to expand...
Click to collapse
Hi krwilson,
It is indeed normal for plemen's build to show T-Mobile. It was most likely extracted from a T-Mobile device at some point. However when you drag the notification area down from the top of the screen it should show Bell Mobility. Just slide your finger from the top of the screen down as if dragging the top bar down.
I also did not have data immediately after flashing plemen's build. I did a soft reset and then it worked perfectly. Regarding the rootfs.img... I downloaded the rootfs.img mentioned a little further into the same thread that mentions an update to get GPS working under Android.
If it shows that you have reception the first thing to try is calling *BELL and see if you get the “your test call was successful” message. If so then you are on the network.
The next thing is a data issue. I would suggest poking your stylus in the reset hole and rebooting. That solved it for me.
Also, I had issues with missing calls on some Android builds (most notably the cupcake 1.5 build). My phone would not ring till 3 or 4 rings on the other end and then very quickly go to voice mail. These issues have disappeared using plemen's “ 1.6 build.
I have everything working except perhaps maybe Bluetooth (not sure I don't really use it). The phone works fine as a phone (calls come through), GPS and data all work. I am very pleased with it.
Best regards,
The Fish
Thank you for the followup.................IT WORKS beautifully! I have not tested BlueTooth yet, no big deal to me either, but it tethers and it does work seamlessly, and fast...........as if it was made for our Vogues.
krwilson said:
Thank you for the followup.................IT WORKS beautifully! I have not tested BlueTooth yet, no big deal to me either, but it tethers and it does work seamlessly, and fast...........as if it was made for our Vogues.
Click to expand...
Click to collapse
What application are you using to tether your Vogue?
PdaNet 2.16
I want to know have can i solve my wifi problems without installing new rom on it.
What is the wireless driver, where are they in my system files?
We can fix the camera issues with changing camera lib files. Can i do that for wifi?
Wifi Problem is ;
I can connect wifi, first it was work fine. After several minutes it dropped and not connect any internet, after several seconds it reconnectted. It always keep going this way.
Can you please help me on this?
What ROM version are you running?
B137 stock and modaco.com/content/huawei-u8800-ideos-x5-u8800-modaco-com/342205/23-june-b137-r3-flb-custom-rom-for-the-huawei-u8800-with-online-kitchen/
I have two of them on my clockwork recovery. Both of them have same issue. I want to try other roms, but its too hard for me to give the time for each rom. So i want to try other roms wifi libs, driver, firmwares.
Not a fan of 137s I've tried so far...You should try these versions:
- V100R001C00B136 (Overseas General version) 2011-05-17
- V100R001C17B160CUSTC17D002 (China Unicom) 2011-04-29
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
To install any of the ROMs, just download the Huawei Firmware you want and unzip it, there should be a folder called "dload" copy that folder and its contents to your sdcard.
Power off phone then hold both volume buttons while powering on the phone, the update should start.
I don't understand why you think it's easier to change a lib/driver and spend a huge amount of time trying to get it to work, when it takes 30 minutes to install a new ROM and all previous applications, if synced with a Google account. When I first got the phone, I've installed like 6-7 ROMs in a matter of hours...
So, in my opinion, you should try the B160 or B136 before you actually start fiddling around with libs.
katu2006 said:
Not a fan of 137s I've tried so far...You should try these versions:
- V100R001C00B136 (Overseas General version) 2011-05-17
- V100R001C17B160CUSTC17D002 (China Unicom) 2011-04-29
To install any of the ROMs, just download the Huawei Firmware you want and unzip it, there should be a folder called "dload" copy that folder and its contents to your sdcard.
Power off phone then hold both volume buttons while powering on the phone, the update should start.
I don't understand why you think it's easier to change a lib/driver and spend a huge amount of time trying to get it to work, when it takes 30 minutes to install a new ROM and all previous applications, if synced with a Google account. When I first got the phone, I've installed like 6-7 ROMs in a matter of hours...
So, in my opinion, you should try the B160 or B136 before you actually start fiddling around with libs.
Click to expand...
Click to collapse
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Özgürce said:
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Click to expand...
Click to collapse
So, stock rom doesn't work too?
Özgürce said:
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Click to expand...
Click to collapse
) I've read your post, but if you think this is windows, where you can just change the wifi drivers, you're in for a treat . The newer ROMs wifi is fine, so whatever you're doing, you're obviously not doing it right or you have a faulty phone.
katu2006 said:
) I've read your post, but if you think this is windows, where you can just change the wifi drivers, you're in for a treat . The newer ROMs wifi is fine, so whatever you're doing, you're obviously not doing it right or you have a faulty phone.
Click to expand...
Click to collapse
I don't understand a thing from your post. Are you understand me?
IF IS A WINDOWS, I CAN CHANGE DRIVER FROM SYSTEM32/DRIVERS. Or install new driver for it. Newer roms are for WHO ? Mine and other my friends in turkey, have same problem. Even they updated the B137 with updata.app from original sources.
Please if you don't know or understand my post, just leave it to be. Obviosly i can't decribe my problem to you.
The whole windows thing was a comparison...All I was trying to say is that upgrading drivers is NOT EASY, as the problem may not be in the lib file.
You better go and learn some ENGLISH, before you try and understand the answers you're given. ) quote "Are you understand me?"
Very very few people have wifi problems like you are experiencing. This isn't to say it doesn't happen as obviously you are having issues, but it's not a rom issues. It's likely that your problem is either a hardware issue with the phone or an issue with your router settings.
Currently there aren't any alternative wifi libs you can try since all the roms are using exactly the same wifi libs which are located in the kernel image, not the system.
I've been experiencing the same problem -international B136 ROM- however I think it may be the router that is the cause of it. Whilst in the main house with the new wireless g router, no issues, everything works fine. In my extension with the old wireless b router the problem happens all the time.
The problem doesn't really bother me to much, but I thought I'd add my 2 cents just in case you were after some more information on the issue =)
guys, I recommend reading my post in the general section with subject "Wifi Client Tuning ... solve connection problem "
Sent from my IDEOS X5
i have simillar wifi problem. When i connect my airties modem,my internet connection is vere very slowly(60-80kpps as speedtest program) How can i fix this problem? Do you think b136 or b160 could fix it?
fukul2027 said:
i have simillar wifi problem. When i connect my airties modem,my internet connection is vere very slowly(60-80kpps as speedtest program) How can i fix this problem? Do you think b136 or b160 could fix it?
Click to expand...
Click to collapse
Definitely, if you've got something like B133, the first thing you have to do is upgrade to 136-137 or 160. You will see huge improvements in terms of Wifi.
is there any problem in b136 or b160? Which one should i apply?
In my view, the best of stock ROMs is B160. The battery lasts longer and it's got less problems.
how can i see my rom version? and do u send offical b160's link?
Go to Settings >>About Phone and scroll down to Build Number. It should look like this U8800V100R001C00B133SP01 and the bit that interests you is B133 or whatever version you've got.
Since Modaco Wiki is down, try this link:
http://www.filefactory.com/f/0f067250fb54623e/
B160 is called China Unicom in that list.
I've managed to get a cached version of Modaco Wiki that is currently down.
http://webcache.googleusercontent.c...&hl=en&ct=clnk&gl=au&source=www.google.com.au
A direct link to b160 from Huawei - http://www.huaweidevice.com/tcpsdow...me=U8800 V100R001C17B160CUSTC17D002(中国联通).zip
My rom seems to b136 is it change anything?
Hi guys,
I recently updated my (german retail) Milestone 2 from 2.2.2 to 2.3.4, original Motorola update.
Since then, I experience problems with my WiFi, a few times per day it seems to disconnect. It still displays WiFi connection, but no data transfer is possible, only switching off and on WiFi helps then.
I tried several possible solutions but none worked so far.
I found that quite a few people solved this kind of problems by replacing files in the etc/wifi folder with files from different Android versions. To me, it would make perfect sense to try the files from the stock ROM with Android 2.2.2 which worked flawlessly before. unfortunately, I have no backup from my phone.
Is there a possibility to get the etc/wifi folder from other MS2 Firmware versions, for example from the .sbf files? I have a few of them handy to try several ones...
I really appreciate your help!
Cheers
Tobi
maybe yo can decompile the 2.2 sbf with moto android depacker and try to mount on linux OS the CG66 (i think that is the system partition)
or maybe use the wifi files from CM7
Sorry for my english..
Thanks for your answer!
I did some experiments in the mean time, replacing singe files never helped. But I also found that the wifi files of custom roms are easily accessible. I first tried CM7 and replaced the complete wifi folder, seemed to work. At the moment, I'm trying the wifi folder from MS2Ginger 4 as it is also Gingerbread and the content of the folder looks more similar to the original Motorola 2.3.4 one. So far, no interrupts, I will report back if this was the ultimate fix.
Cheers
Tobi
Hi all, here I wish to continue porting OmniROM from the P4/P4wifi over to our device the P5/P5wifi.
*Please note that this is simply a port of an already built rom. It was not built from source therefore anything that you may find to be broken will more than likely remain broken until it is fixed in the parent ROM.
-Many thanks to the builder of this rom @AAccount. His hard work made this ROM possible. :good:
-Thanks to @jolinnard whose kernel is being used in these ROMs. :good:
*On first boot the keyboard will not be showing. The fix is simple. Go to settings>Language & Input. Tap on Current Keyboard and flip the toggle next to Hardware. The keyboard should now be fine.
Working:
Everything works on the P5 AFAIK
Not working:
SELinux---------Need a recovery that supports it.
To those looking forward to a P5 3G rom then please note that there will not be one any time soon. AAccount has stopped building for the p4 3g so that means we don't have a 3g rom to port anymore. So unless AAccount starts porting for the p4 again there won't be a P5 rom.
Flash Instructions
Wipe data, system, cache, dalvik if coming from another ROM. If ugrading to a newer build then a simple Dalvik and cache wipe will do
Flash the ROM zip
Flash GAPPs (Thanks to @jolinnard)
Flash SuperSU
Reboot and enjoy
Original ROM thread
Credits
@AAccount - for the ROM
@jolinnard - For the kernel
@decatf - for his work on the p4 kernel which is used here that delivers great performance
If you helped out and I missed you in the credits then send me a PM and you will be credited
This port has been discontinued!!
"See why
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
@L3Ron ,i will give it a try.
@jolinnard
If you want to port or start with omni source? Nice to See your work for our Tab 8.9.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
Awesome!! Erased my internal sdcard by accident last week. Luckily I have the same files on my Nexus 9 so I was saved. This port works great for me. Should I even port for the P5? AAccount stopped building for the p4 as of May 23. Reason being that 3G doesn't work but oddly enough it does work on the P5 using our modified KK kernel and your data_on script.
bierma32 said:
@L3R0N ,i will give it a try.
Click to expand...
Click to collapse
Great. Tell me how it works for you.
L3R0N said:
Great. Tell me how it works for you.
Click to expand...
Click to collapse
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
bierma32 said:
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
Click to expand...
Click to collapse
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
julen163 said:
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
Click to expand...
Click to collapse
I tried different setting at the advanced configuration of WLAN settings with out success.
bierma32 said:
I tried different setting at the advanced configuration of WLAN settings with out success.
Click to expand...
Click to collapse
I have no such problems. My WiFi connects just fine. Try turning airplane mode on for a moment then turn it back off and try connecting again. Could it be the kernel? I'll p.m you a kernel to try and see if it fixes anything later on. Any logs?
OP has been updated with links to the new build released by AAccount today. According to him there were no major changes, just the usual Omni sync.
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Edit: used the sideload option with ADB and used the omni-5.1.1-20150706-p5wifi-HOMEMADE ROM
Got also problems with the WiFi connection. My network uses 192.168.2.xx range
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
No you are not the only one. This was reported to me earlier today by another user. I'm in the process of uploading a new zip to androidfilehost and another to mega. They will be up soon.
Nonomen said:
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Click to expand...
Click to collapse
I'm sorry to hear that. You can use adb to push a zip file to your sdcard for installation.
Use this command
Code:
adb push romname.zip sdcard
Or you could use sideload to install one as well. in twrp go to advanced then select adb sideload and connect your tab to your pc. Open up windows command prompt and type
Code:
adb sideload romname.zip
This should get a rom installed to your tab.
File has been re-uploaded. It opens fine now and should work fine.
L3R0N said:
File has been re-uploaded. It opens fine now and should work fine.
Click to expand...
Click to collapse
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Nonomen said:
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Click to expand...
Click to collapse
I have absolutely no problems with the ROM. No force closes or anything. Can you try a clean install of the 0716 build and see if it fixes anything?
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Nonomen said:
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Click to expand...
Click to collapse
There aren't any huge differences but here are a few notable changes
1) Ability to change battery icon
2) Battery color changes based on charge level
3) Pre rooted
4) Performance settings app included
5) Omniswitch recent
And a few others nothing big. IMO I prefer the browser in the omnirom over the aosp browser and the omni keyboard over the Google keyboard in the aosp ROM. But that's personal preference. Try both and pick a side *twix ad*
how i can use this rom for the p5 ?
thanks
4rch0 said:
how i can use this rom for the p5 ?
thanks
Click to expand...
Click to collapse
Edit the updater script and at the top where you see p5wifi simply delete the "WiFi" part so only p5 remains. Save the file put it back into the ROM zip and flash. Or you could simply flash the p5wifi recovery and you'll no longer have to worry about editing the script.
For future ROMs I think I'll remove the assert lines in the updater script so nobody else will have to worry about them.
Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
I think I figured something. Everytime I attempt to make a phone call on this, I get to choose from which sim card should I dial, #1 or #2 , but what I have noticed now is that I am being asked "SIM1" or "Slot2" ... SLOT 2 I thought? That may be the reason that audio routing doesnt work well for this... tried searching build.prop but this string is not there and I just dont know where to search for this string to get this fixed, anybody can chime in?
Thanks
Did you figure it out ? As i have the same problem with the same rom in addition that when i call anyone and he is on a call i don't get notified with " call waiting
Mr.Ultimate said:
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
Click to expand...
Click to collapse
Which CSC did you choose?
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Mr.Ultimate said:
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Click to expand...
Click to collapse
Well, i know that mixer paths are different on single sim and dual sim phones.
Can you extract from stock rom the file "/system/etc/mixer_paths.xml" and overwrite the one in custom rom ?
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Mr.Ultimate said:
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Click to expand...
Click to collapse
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
zlazaar said:
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
Click to expand...
Click to collapse
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Mr.Ultimate said:
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Click to expand...
Click to collapse
Path : /system/csc
Indeed, conflits may happen. But just dump it and let we examine it.
Ok here is what I managed to try, I backed up stock rom android 5.0 all working state mixer files from etc dir, then flashed magma rom again, backed up those same files for restoration to working state, replaced files with ones extracted while on 5.0 stock android, reboot device, no sound whatsoever, phone wont even buzz keypad dialtones or connect dial phonecalls just hangs. So I went and restored back original magmanx rom mixer files, reboot, but still no success... so now I have just finished restoring 5.0 again, will dump csc folder and share with you. will also need to charge my battery a bit because @ 30% cant expect much to happen when flashing magma nx...
Thanks for the help amigo!!!
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Mr.Ultimate said:
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Click to expand...
Click to collapse
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
zlazaar said:
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
Click to expand...
Click to collapse
amazing, will try in few mins
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Mr.Ultimate said:
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Click to expand...
Click to collapse
Did you checked correct permissions before reboot ?
I'm afraid the problem is deeper than mixer paths.
I'll try to digg more.
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Mr.Ultimate said:
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Click to expand...
Click to collapse
The file "mixer_paths.xml" must have permission set to 0644 (like other files in /system/etc directory).
And try darklord Kernel.
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Mr.Ultimate said:
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Click to expand...
Click to collapse
Sorry i just noticed you already have darklord kernel.
And set permission like other files in this directory (if not already done by your file manager).