Related
I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/
Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.
Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!
woohoo custom ROMs already. Guess I'll be getting myself the phone after all.
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.
That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.
psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.
they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?
Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..
[Jan 12][DL DesireZ v2.2][NAND][PPP/RMNET][Base 1.72.466.4][SquashFS][UTF8&Arabic]
CAN SOMEONE PLEASE CLOSE or DELETE THIS THREAD. Dandiest has started his own thread here on the NAND forum and this is no longer needed.
TO ALL: I am reposting a NAND build from the SD forums for Dandiest. His work is fantastic and this is the most stable build I have used to date at least for me and my TMOUS HD2.
Orignal thread: http://forum.xda-developers.com/showthread.php?t=881937
Dandiest does not want to maintain 2 threads but I will be updating this one as he updates his so that the same content is there. If you want to pose a question to Dandiest you will need to do it in the original forum.
Just try it, you will know.
News
12/01/2011
- Bug fix for both SD and Nand build(reloaded). update.bugfix.1201201101.7z
for SD build, only need to extract the folder in desire_z to overwrite your current desire_z folder.
for Nand build, extract the folder of .data and DLZUPDATE to the root of your SD card, you can edit the config.txt in .data to change the gps_zone. and can put your original data.img into .data.
Code:
[COLOR="Red"]
11/01/2011
Made a lot of changes, refer to the change-log below, but the upload stuck at 50% last night when upload to multiupload in order not to split the package, sigh.
Reupload today.
10/01/2011
Made some changes based on the feedback of the Nand version, am reuploading it now.
For SD build users, can not find a way to mount the yaffs2 image and no unyaffs can be found on android, thus, I have to convert it to ext2 version, who has a linux box and fast bandwidth, please contact me, thus, I only need to upload the nand version, you help me convert it to ext2 and upload. :D
[/COLOR]
09/01/2011
Nand V2.0 Testing version released, and SD will make use of the same system.img:
1. this is the test version only , but I have used it for > 1day, and quite proud of it. :D
2. I have built in with the "upgrade" facility, thus, willl provide the update for some enhancement soon, together with SD build.
3. I have enabled the Data2SD(need test, as it is most easy to do :D, thanks for Takaaki), can refer to other build for how to use it, but I have extended the .config to be able to choose from Data2 SD or data2ext4 which will be enabled soon, suggest you partition SDCard before implementing the Data2Ext4.
4. If you encountered any FC or Market problem or Any other problem, can use the same approach as SD version, do the fix permission in the Rom Manager.
5. the previous update for reverting back to stock version is still applicable to the Nand build, put the update in the folder of "DLZUPDATE" at the root of your SDCard.
6. have re-squashed the build, put some apps(Music, etc) aside in the system/app directly in order for you to replace it. others, still keep the symbol link to Squashed file, that enable you to delete the link and put your own app.
7. several not so common apps and skin have been removed, will provide it late to the data partition.
- made 2 builds, same system base, one for SD, the other for Nand. I will try to maintain 2 builds in sync going forward.
- for the system base, i made a lot of changes, some problems should be solved, but need more tests.
- for nand version, i squashed as many files as possible but keep the some level of the flexibility of customization, e.g, for app, i changed the symbol link from directory to filles, thus, you can easily overwrite a symbol link with your own app, for framework , same approach, you can also change anything you like.
- after squashed, the system is about 200mb, next i will incorporate into the data2ext4, to improve the I/O and of course, enlarge the data space.
- Provide 1G data.img. [ATTACH]476315[/ATTACH] to replace your existing one.
- If you still experience the FC. try (thanks nito2721)
Open the "Terminal" app from the application drawer. Type:
su
fix_permissions
- FOR TMOBILE users please check [URL]http://forum.xda-developers.com/showpost.php?p=10186545&postcount=708[/URL] thanks to TheGeorgiaSwagger
Changlog
Code:
[B]v2.2[/B]
- fix the boot problem and revert the kernel back to 8.6 for SD build.
- fix the data2sd, and add the data2ext4(need test).
[B]v2.1[/B]
- fixed the boot time too long for v2.0
- add rmnet support, can change easily by: touch /system/ppp to change to ppp, or just rm it for rmnet.
- fix the bug (can not process the update correctly) in initrd.gz for nand.
- add feature in initrd.gz for SD to automatically create 1g data.img.
- some other changes.
[B]v2.0[/B]
- Major release.
- Use same base with my nand version, which Squashed as many files as possible.
- Even for squashed file, it still can be replaced as the separated symbol link is kept in original place.
- New Kernel of MDJ 9.2 in order to support SquashFS and Ext4.
- System.ext2 is hence recreated with about 290M + 30M spare space, which is about 100M less than the unsquashed version.
[B]v1.0[/B]
- Major release.
[B]v0.3.2[/B]
- Optional Bugfix for high mic gain problem.
[B]v0.3.1n[/B]
- Pre-configured build for newbie.
- Reset all the file permissions to prevent any possible FC.
- Incorporate all the incremental updates except the Optional ones.
- Google Voice search.
- And more..
[B]v0.3.1[/B]
- An optional update to customize your own boot animation.
- An optional update to install the Stock Widget
[B]v0.3[/B]
- [B][COLOR="Red"]advanced power menu[/COLOR][/B]
- [B][COLOR="red"]totally rotate[/COLOR][/B]
- remove Swype from system to data
- many optimization
- this is considered as a major release.
[B]v0.2.2s[/B]
- Optional update for revert back to stock framework.
- Optional update to install Stockwidget.
[B]v0.2.2[/B]
- Include Bugfix 2010122501(auto APN)
- Add HTC stock widget
- Remove Wifi Call
- Supply some applications to be installed into data.img.
.Gmail
.Google maps
.Google translate
.current widget
.Astro file manager
.Audio widget
.Drocap2
.Quadrant benchmark
.Sms backup plus+
.some Skins
[B]v0.2.1[/B]
- Bugfix 2010122501(auto APN)
[B]v0.2[/B]
- Fixed the wifi issue and added the Ad-hoc Wireless Network Support.
- Fixed the SU issue.
- Used full stock Rom to recreate this build.
[B]v0.1[/B]
- Initial release.
Features
- Cedesmith new Initrd
- Hastarin r8.6 kernel
- Fly animation
- Latest busybox
- camera
- Massive APN from Cyanogen ROM
- Wifi fixed and added the Adhoc Wireless Network Support.
- UTF8, support multi character languages, e.g. Chinese File name etc.
- Buildin Arabic & Hebrew support
- all that work in other builds.
Download:
V2.1 for Nand
http://www.multiupload.com/PEWNGWULCX
Apps removed from V2.1 build:
http://www.mediafire.com/?vjb479v6k0mougn
For Nand build, please extract it in "DLZUPDATE", remove the apps that you may not need before reboot.
For SD build, extract it to your android folder.
IMPORTANT!
1. After first boot, open the ROM manager and run Fix permission(you can use it to fix the FC late once it happens.)
2. Reboot.
3. Use setCPU to set the CPU to 99840 or even more.
4. Install your apps
5. For stock version fans, apply the 2 optional updates I provided in "Bugfix&New Features"..[/B]
SD build V1.0
http://www.multiupload.com/E8PC0MZDW0
- please extract the "desire_z" to your sdcard
- put the AndroidApp into that folder only after you successfully boot this build.
- additional keyboards are provided in the AndroidApp, select either one you prefer.
- For stock version fans, apply the 2 optional updates I provided in "Bugfix&New Features".
Bugfix&New Features
Thanks to:
- Cedesmith
- LeTama
- Hastarin
- NetRipper
- Markinus
- gauner1986
and others
Installation:
- extract "desire_z" folder on the root of your SD card
- Run "CLRCAD.exe" then "haret.exe"
This build should be very fast and smooth, I got the Quadrant score of 2700.
the screen is similar to Desire HD, you can refer to the screen shots from MDJ's build, only difference is battery with percentage which I think is most important.
Enjoy
the rom seems no FM Radio !!!
wpullo said:
the rom seems no FM Radio !!!
Click to expand...
Click to collapse
dandiest included all of the apps he ripped from this build above. Reposting his link....
http://www.mediafire.com/?vjb479v6k0mougn
to install FM radio you need to use the built-in update utility dandiest created. In the root of your SD card you must create the following folders, "DLZUPDATE" inside that create "root" inside that create "system" inside that create "app" inside that place the file "com.htc.fm.apk."
Once you have DLZUPDATE\root\system\app in the root of your SD with the com.htc.fm.apk file inside, reboot your phone and it will automatically install the FM radio.
I've tried every nand build and this one is by far the greatest. Fast, stable, lightweight and extremely low battery consumption. Feels like the native OS. You can read other user's testimonies and if you'd like to follow dandiest's incredible work, he maintains this build in the HD2 Android Development section.
Question
How about TMOUS MMS 1024K pic size fix, is it implemented?
tjones25 said:
How about TMOUS MMS 1024K pic size fix, is it implemented?
Click to expand...
Click to collapse
Yes. Pictures larger than the max (1024K) will be compressed to ~40K. Anything smaller than the max will be sent out without being compressed. I have it running 100% from nand on my TMOUS HD2. You can also run it from your SD through WM (which i used to before magldr) and he also created a data2sd build for euro hd2 users.
Everything has been addressed in dandiest's thread. He maintains and focuses on this build only this build to make it perfect and in my opinion, he has. dandiest has expressed that he doesn't want to maintain two threads so please head over to the following link to his thread. You will not be disappointed.
http://forum.xda-developers.com/showthread.php?t=881937
fatappel said:
Yes. Pictures larger than the max (1024K) will be compressed to ~40K. Anything smaller than the max will be sent out without being compressed. I have it running 100% from nand on my TMOUS HD2. You can also run it from your SD through WM (which i used to before magldr) and he also created a data2sd build for euro hd2 users.
Everything has been addressed in dandiest's thread. He maintains and focuses on this build only this build to make it perfect and in my opinion, he has. dandiest has expressed that he doesn't want to maintain two threads so please head over to the following link to his thread. You will not be disappointed.
http://forum.xda-developers.com/showthread.php?t=881937
Click to expand...
Click to collapse
I was using the sd version, but switched build for nand...glad to see this build in nand format
change font?
i want change font, but it error?
kenzi_100c said:
i want change font, but it error?
Click to expand...
Click to collapse
font folder is squashed so it can not be changed by normal means. if you ask the build creator to make you a font update folder to use with his update utility, he will.
his thread is here if you'd like to request.....
http://forum.xda-developers.com/showthread.php?t=881937
I'm getting freezes galore on the NAND version... Not sure why, but I've downloaded it 2 times, re-installed like 4 times, but it just doesn't want to run on my device. It does run very smooth when it works for the 5min that it works though.
I have not had that issue but lets get some basics. What verson of Magldr are you using and how many times have you reflashed and/or rebooted your phone.
haha, thanks, just find this thread.
I really have no time to maintain 2 threads, instead, I'd rather spending all my spare time to improve the build itself.
a lot of time has been spent on enabling the data2sd and ext4, now, I'm excited to release the upgrade(test version) to V2.3, it is not anything like the current data2sd or ext4 or a2sd(I have studied all of those) , what's special for my build is:
1. it can be easily change from data2sd to ext, vice versa by the switcher of data_img in config.txt, if the sdcard has 2nd partition, it will automatically change to the data2ext.
2. sd card is not simply mount to overwrite the nand data partiton, instead, the original data partition in Nand is used for improve the system performance: property, misc, system, dalvik-cache are moved back to nand, no matter the data is in data.img file or on 2nd partition.
3. a switcher of "sd_boost" in config.txt is provided to improve the SD performance furthermore. for ext4, it will be mounted to loop without journal, which will significantly improve the SD IO. for data.img, a-sync will be used. while of course, the price is that there is some chance of data crapt, for data.img user, can easily copy the file, for ext user, I will provide another function to backup/restore the data in ext to/from an img file soon.
I was wondering if i could remove the animations and get the stock one?
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
That audio routing thread is in the RHOD section, and I've only tested it on a RHOD - but AFAIK it should work on other devices. Let me know.
I just trying it....after 1 hours in initial boot proses my battre was drain..and until now i never pass the initial boot
I think FRX06 best for my RAPH100 , but it can frezze if i put sim card..any idea to add my APNs mobile Network manually on FRX06?but i don't know how to do it?
Initial boot (no SIM)
Very nice! Just upgraded/updated new data.img to include grabbing the new kernel package (1340), rootfs and system files! I haven't tried anything that accesses data yet (ran it with no SIM) but FRX07 seems very stable on the RAPH100. However, it took a tad longer than what I'm used to on initial boot. Going to format and try with no androidapps folder and no media folder and see if that's what cuts down the initial boot. All in all awesome job... but something tells me you already knew that...
R^7Z said:
Very nice! Just upgraded/updated new data.img to include grabbing the new kernel package (1340), rootfs and system files! I haven't tried anything that accesses data yet (ran it with no SIM) but FRX07 seems very stable on the RAPH100. However, it took a tad longer than what I'm used to on initial boot. Going to format and try with no androidapps folder and no media folder and see if that's what cuts down the initial boot. All in all awesome job... but something tells me you already knew that...
Click to expand...
Click to collapse
nice report..but i wanna know if you boot with SIM card..it's freeze your device?
If it freezed with FRX06 it shouldn't freeze anymore,hyc/highlandsun's ril solved it..
it very stable, but maybe someone tried install a new Market app?
GoldAngelo said:
it very stable, but maybe someone tried install a new Market app?
Click to expand...
Click to collapse
I haven't, give it a shot - I asked the same thing before release .
system doesn't detect my SIM, it said "No service" despite my SIM operated normally in WinMo
datbi_201 said:
system doesn't detect my SIM, it said "No service" despite my SIM operated normally in WinMo
Click to expand...
Click to collapse
What phone? Have you set the phone to be on GSM mode in Android...?
arrrghhh said:
What phone? Have you set the phone to be on GSM mode in Android...?
Click to expand...
Click to collapse
i'm using Ral, i installed FRX06 last week and everything was ok w/o any setting. But now with FRX07 ...
i re-run Haret from WinMo but it hang up with command "(something): read retry", so i thought that my SDcard maybe corrupt. Just re-formated and re-run Haret.
it stopped/paused too long with command: "htc_cable_notify_do_work: 0"
and now, it's hanging up completely with "r5:00000000 r4:00000000"
what'd i do
tks
Please try what was asked in the previous post and report your findings. The change logs in the first few posts make mention of a framework change. Meaning FRX07 might require some additional setting changes, depending on your phone/device...
By the way, what's a Ral? I have a RAPH100 and a RAPH110, which one do you have?
Well done with this build! It seems that the WiFi Turn Off- Turn On - Doesn't work anymore bug is gone (for my RAPH100).
LE: And it seems that the clock network sync bug is gone, too.
R^7Z said:
Please try what was asked in the previous post and report your findings. The change logs in the first few posts make mention of a framework change. Meaning FRX07 might require some additional setting changes, depending on your phone/device...
By the way, what's a Ral? I have a RAPH100 and a RAPH110, which one do you have?
Click to expand...
Click to collapse
i have Raph100 and i followed all steps carefully but install progress still hang up
First of all, great work on this guys! I've been waiting for quite a while and this release works great on my RHOD400.
Onto my feedback for the RAPH800...
I can't boot the kernel that's bundled with the 7/16 release.
It boots with endless repeat of "OOPS - smd_tty buffer mismatch"
I went back through a few kernels from the build page. Each of the following builds boot with the same error
htc-msm-linux @ 20110716_005117
htc-msm-linux @ 20110711_082424
htc-msm-linux @ 20110627_223755
When I got to this build:
htc-msm-linux @ 20110622_180615
The boot froze for a while (~30 minutes) and I finally reset the device. It booted fine after the reboot.
I'm not sure if this information helps at all, but I hope it helps in pinpointing a problem what changed over this range of builds.
Again, thanks so much. I'm looking forward to testing FRX07! I'm thinking I'll be able to use it daily on my RHOD!
Superuser permissions, heck yeah! That's been one of the more annoying things about xdandroid; some apps just don't like how it does root, which I suspect might have something to do with the lack of the aforementioned app. Plus, it's just not safe having su be autoconfirmed. I appreciate it.
Can fellow Raph100 owners verify if the physical keyboard lights are always on in closed position? When drawn, the lights goes off which is the reverse of how it should function. The LCD panel doesn't turn off fully as well, it's lit slightly.
Otherwise, it's a good stable build. No SOD's yet with the stock kernel. The device is not warm on standby as well compared to the previous build installed. DroidWall works out of the box without the usual tweak as well.
Thanks & kudos!
agibby5 said:
First of all, great work on this guys! I've been waiting for quite a while and this release works great on my RHOD400.
Onto my feedback for the RAPH800...
I can't boot the kernel that's bundled with the 7/16 release.
It boots with endless repeat of "OOPS - smd_tty buffer mismatch"
I went back through a few kernels from the build page. Each of the following builds boot with the same error
htc-msm-linux @ 20110716_005117
htc-msm-linux @ 20110711_082424
htc-msm-linux @ 20110627_223755
When I got to this build:
htc-msm-linux @ 20110622_180615
The boot froze for a while (~30 minutes) and I finally reset the device. It booted fine after the reboot.
I'm not sure if this information helps at all, but I hope it helps in pinpointing a problem what changed over this range of builds.
Again, thanks so much. I'm looking forward to testing FRX07! I'm thinking I'll be able to use it daily on my RHOD!
Click to expand...
Click to collapse
I can't get my RAPH800 to boot at all! Might be a deeper issue with the device tho. Your info does help, I needed someone to narrow down when the issue first started. Thanks!
AGPS Patch HTC ONE X 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SAT
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samsung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
The patch works great for a few users thus far. I want to confirm that further before making this an officially supported device.
Consider testing and letting me know!
Donations always welcome for supporting the backend of the system.
Is this the same as the gps fix posted in this section earlier?
Cxpher said:
Is this the same as the gps fix posted in this section earlier?
Click to expand...
Click to collapse
No, mine actually removes a lot of what I've proven to be inconsistent points and operates using reliable servers for time and data. This assumes you use the v3.x trunk which is currently at v3.1. As always, I suggest the Google NO-SSL Build.
Won't go through the whole description and theories again because I've done so about 50 times on the other threads. However, it is discussed in minor detail in the Notes Section.
My patch has been downloaded over a million times and is either incorporated in or an add-on to a large number of ROM's.
Further, this patch has served over 10 million xtra.bin downloads and 14 million NTP DNS requests.
EDIT: For those who don't see that this has been an ongoing development and really successful thread, scroll to the bottom of the first post and review the 20+ devices officially supported. There are a number of tentative support devices out there, too, which I didn't feel were successful enough or were too old to be useful in time spent supporting them.
No they are not the same one. As far as I know crypted has his own ntp-setver.
MarcoHD said:
No they are not the same one. As far as I know crypted has his own ntp-setver.
Click to expand...
Click to collapse
NTP server and XTRA.BIN provisioning as well...
Damn Crypted...did you also get an HTC One X now? I'm also thinking about possibly getting the One X. But i didn't know it had GPS problems.
I still can't thank you enough for all the work you did with the Prime!
babymatteo said:
Damn Crypted...did you also get an HTC One X now? I'm also thinking about possibly getting the One X. But i didn't know it had GPS problems.
I still can't thank you enough for all the work you did with the Prime!
Click to expand...
Click to collapse
Nah, I don't have the device. I may get one eventually, but strapped for extra cash in my technology account at the moment.
I worked with someone via private message to make sure this patch was a-go at the users request. He was a user of my work on another device before buying this phone. Anyway, it worked fine so I figured it would be helpful to get this out to others too.
EDIT: Once this goes to fully supported, I think that puts me at 25 concurrent devices supported. Not too shabby.
Yep, same results as on HD2 and Sensation XE - first cold lock ever on my new One with this patch in 18secs and subsequent locks in 3 or 4 secs. Number of sats available more than normal too at x/16. This really is a fantastic patch - I use GPS a lot (iGo, MapMyRide, Maps, etc) - wouldn't be without it now, and congrats on some of the best dev support/involvement have seen recently on XDA, well done and thanks
Great mod. Worked amazingly in my hd2 and sensation days.
Luckily my galaxy note and one x lock in 2-3 secs without the need of this mod this time however great worked though, hopefully helps others out and great for the community
Sent from my HTC One X using XDA
I picked up this phone last night at Vodafone CZ (1.26.401.2) it even includes urBeats as a freebie. Not too bad at all considering it is the cheapest price I was able to find in the country.
Anyway, I have no point of reference but coming from a DesireHD, it seems that this does lock pretty quickly and accurately. As the previous user has said though, the phone may not need this patch as much as other devices do, but what the hell, I can always go back if needed.
For the record, the ADB Push method didn't work for me. It gave me multiple errors with permissions and the like. I am currently running ARHD 1.2.2 so did it the manual way.
Not sure if it's something on my end, or the script needs revision
Quiksilver78 said:
I picked up this phone last night at Vodafone CZ (1.26.401.2) it even includes urBeats as a freebie. Not too bad at all considering it is the cheapest price I was able to find in the country.
Anyway, I have no point of reference but coming from a DesireHD, it seems that this does lock pretty quickly and accurately. As the previous user has said though, the phone may not need this patch as much as other devices do, but what the hell, I can always go back if needed.
For the record, the ADB Push method didn't work for me. It gave me multiple errors with permissions and the like. I am currently running ARHD 1.2.2 so did it the manual way.
Not sure if it's something on my end, or the script needs revision
Click to expand...
Click to collapse
This patch works on 25+ devices. It would require over a hundred individual zips to ensure all methods worked with each device.
Because of the major headache above would be, I detail three installation methods.
Sent from my Desire HD using XDA
Hello everyone,
I just installed your patch (the Google Specific No-SSL v3.1) in Clockworkmod Touch Recovery 5.8.2.7 but i got a message : "E:Error in /sdcard/agps.patch.google.build.nossl.v3.1.zip
(status 0)
Installation aborted
and the problem is that my phone is not booting anymore.
I unlocked my bootloader and installed latest CWR.
I can boot in the bootloader and in recovery mod but i can't get access to sdcard in anyway to put any rom on it and flash the system.
adb is not working and you can't mount usb storage in CWR.
This is probably stupid but i don't know how to get something to flash in the device.
Any idea please ?
bece65 said:
Hello everyone,
I just installed your patch (the Google Specific No-SSL v3.1) in Clockworkmod Touch Recovery 5.8.2.7 but i got a message : "E:Error in /sdcard/agps.patch.google.build.nossl.v3.1.zip
(status 0)
Installation aborted
and the problem is that my phone is not booting anymore.
I unlocked my bootloader and installed latest CWR.
I can boot in the bootloader and in recovery mod but i can't get access to sdcard in anyway to put any rom on it and flash the system.
adb is not working and you can't mount usb storage in CWR.
This is probably stupid but i don't know how to get something to flash in the device.
Any idea please ?
Click to expand...
Click to collapse
This patch cannot do this to any device. Status 0 means it did not even install. There is something else wrong causing your issue.
Consider revising your steps for your last ROM install and/or your unlocking process.
The only suggestion I have for you is to try to do a factory reset/wipe of the device.
We cannot support your non-GPS issues on this thread. So, contact the ROM, unlock tool, and/or bootloader dev threads.
ok, thanks for your quick answer.
Do not understand why AGPS shuld be used on One X, my One X have GPS signal when Sygic starts. Sems to be faster than my DHD with fix so far. impressive
audiavant said:
Do not understand why AGPS shuld be used on One X, my One X have GPS signal when Sygic starts. Sems to be faster than my DHD with fix so far. impressive
Click to expand...
Click to collapse
I do not understand your comment. Are you saying the device doesn't have aGPS functionality so this patch isn't useful? Are you saying that this patch isn't necessary because you have success with your unit compared to your prior DHD? Or, what are you saying?
This patch has been necessary for a number of users and this is the only reason why I brought this to the One X Dev forum...
You may find this helps you out even more, not sure. I'm not so lucky as to have a great phone like this. I'm still on the old Inspire 4G.
nickyg008 said:
Great mod. Worked amazingly in my hd2 and sensation days.
Luckily my galaxy note and one x lock in 2-3 secs without the need of this mod this time however great worked though, hopefully helps others out and great for the community
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
same here, i'm getting a lock in 3 seconds without this patch, seems like htc have got their act together on this issue
but the patch worked wonders on my old Desire so well done crypted for that
beanbean50 said:
same here, i'm getting a lock in 3 seconds without this patch, seems like htc have got their act together on this issue
but the patch worked wonders on my old Desire so well done crypted for that
Click to expand...
Click to collapse
I'd say that it is still ROM dependent, too. But time will tell. I hoped that this patch would be useless by the time ICS reached devices. That didn't come true. Maybe soon though!
Sorry for confution, this patch is usfull for all having slow gps problem.
Ment to say my One X work perfect without fix.
Used this on my DHD and it improved gps signal a lot (10 times faster signal), had a loock into file to understand what it dos and it give region specifick gps satelit info as original not have for your region.
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Guys, as you can see further in this thread, someone donated a fully working HD2 to me. Just like that. For free.
If you ask me, this is an act of an incredible generousity.
Thanks a million, Legion.X. I'm still to find a way to thank you.
Let the development continue!
Introducing Common Sense 4.1
link to ver. 0.2:
http://www.mediafire.com/download/75m6jwtcq28gg8u/CommonSense41_next.zip
please test and comment.
previous versions:
ver 0.1: https://mega.co.nz/#!WhpRzJQa!DOdybh...6N52mPTfNkXk1k
what works:
* full Sense 4.1. almost everything works. daily driver.
* silky smooth, as good as native. flies at 20-30FPS with live wallpaper, probably around 60FPS with still wallpaper
* fast and snappy.
* sound recording works. voice input works. BT works.
* full 3D Rosie
* live wallpapers, Sense lockscreens etc.
* EXT2 over YAFFS loop (works automatically out of the box)
* should be snappier than ver. 0.1
known problems:
* it does reboot randomly from time to time. I'm looking for ways to solve these... looks like we'll end up recompiling libs from source.
ANYONE WHO HAS EXPERIENCE AND/OR WORKING ENVIRONMENT TO RECOMPILE FILES FROM SOURCE, PLEASE PM ME. My goal is to take gralloc sources from CM9 and adapt them for sense. but I don't have linux and don't have the toolchain set up. I'd appreciate any help with this.
* probably won't work in full NAND on TMOUS. anyone who wishes to participate, please try to install on TMOUS without sd-ext and report what you get. logcats are most welcome!
* WiFi router doesn't work. Custom routers from Play Store should work.
* Video shooting works at 15FPS. Don't know if that can be fixed... for me 15FPS is fine anyway
next steps:
* hopefully fix some of the crashes
* fix terrible lags during initial configuration and in the setup wizard
* improve Rosie (I know how to make it even smoother )
* try crossbreeder
* install XPosed framework
* please suggest more things to improve!
installation:
* BACKUP!!!
* IMPORTANT: you need CWM 3.0.0.6.. Other recoveries may or may not work. voronkov_pavel reports that CWM touch recovery beta 8 does not work with this ROM.
* REMEMBER: for Data On Ext, keep your system partition small! philliped364 reports that 55MB works just fine
* install Common Sense from recovery
* reboot. the first boot will take a while (although it's waaaay faster than in other ROMs thanks to odexing). should boot in 2-3 minutes. if it doesn't boot within 10 minutes, please report
* wait for the lockscreen to appear. DON'T PULL THE RING YET!
* make some coffee. let your HD2 settle down for at least half an hour
* pull the ring to unlock. if the setup wizard does not appear immediately, don't touch the device for another half an hour. if the device reboots by itself, please report.
* complete the setup wizard. it will lag. please be patient. DON'T SIGN IN TO YOUR GOOGLE ACCOUNT YET! finish the wizard and let Sense load.
* wait for two minutes and reboot
* let it settle down for another half an hour. it will optimize the databases during that phase. don't try to work with the device. it will lag terribly.
* unlock, go to Settings -> developer's settings, scroll down, disable "force GPU rendering"
* reboot
* your device should be fully functional now. now go to Settings -> accounts and sign it to your google account, email and whatever you like
big thanks to Legion.X (for sending me his HD2 for free), philliped346 (for his immense help and making my ROM nativeSD), saurabhrendale (for his incredible animations), Mr Evil (for letting me kang sound files from his EvoHD2 ROM), ckpv5 (for letting me kang Sense files from his MyOneDx ROM), dorimanx (for his kernel), RobbieP, ya5, aazzam16661, Daekin and many, many others for helping me out.
Some technical details about the ROM:
Config: Data on Ext, DB on NAND, looped over EXT2.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
Sense: mostly myONEdx RC4.0 FX+ ROM. Rosie modified by me. Some files taken from stock Desire X ROM.
A word about kanging:
my goal is to create a stable Sense 4.1 base for HD2. feel free to kang anything you find here. just please PLEASE give proper credits. don't forget the guys who gave me some of the files: Mr Evil (creator of the EvoHD2 ROM) and ckpv5 (creator of the MyOneDx ROM)
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Enjoy.
Report bugs.
May the Force be with you
thelonewolf_pav said:
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Here's the link. Enjoy.
http://d-h.st/7MZ
Disclaimer:
Frankly, I don't even know if it boots the way it is now. I was in the middle of something when this happened. Most probably, it will just work though.
Technical details:
Config: Data on Ext, DB on NAND, looped over EXT2. Yeah, it's returded fast.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Sense: stock Desire X ROM. I've got permission to use MyOne ROM (see Desire X forum), it has full 3D effects enabled and runs smooth as silk on HD2 (it's pretty damn smooth even with live wallpapers!)
What should work:
Everything. I know that WiFi router doesn't work, but that's it, more or less. Video shooting works at 15FPS. Sound recording works. Voice input works. BT works.
Known problems:
It does crash from time to time. Needs more work on system files. I was planning to recompile gralloc from CM9 to use it here, but didn't have the privilege to finish that.
For EXT2 loop to work, one needs to add creation of an empty data.img file in /Data/Data folder. Make it as big as possible. Format it for Ext2. The rest will be done by init.rc
............. Well, that's it. I'll be watching this thread. Don't ask me to develop anything though, I can't do anything without a working HD2. Sorry guys and good luck to anyone who will take it from here.
Bye
Click to expand...
Click to collapse
I will continue your hard work with Daekin
I've been working on Desire X Sense 4.1 port so, this will fix BT for us(build prop)
Thanks
Cant Install
Hello,i tried installing this rom but i couldnt..i get E:error in sdcard/commonsense41..zip(status6) any ideas?
blackphoenix50 said:
Hello,i tried installing this rom but i couldnt..i get E:error in sdcard/commonsense41..zip(status6) any ideas?
Click to expand...
Click to collapse
I cannot check for an obvious reason, but my gut feeling tells me that you downloaded a corrupted file. Try to open it with winzip. if it opens, extract the files and pack them back.
or just download again....
thelonewolf_pav said:
I cannot check for an obvious reason, but my gut feeling tells me that you downloaded a corrupted file. Try to open it with winzip. if it opens, extract the files and pack them back.
or just download again....
Click to expand...
Click to collapse
I did all these but still cant install.....tried also with twrp it gave me an error about updater binary...i searched at google and i think that the problem is the updater-script file...could someone plz check it cz i dont have the knowledge for that....
thelonewolf_pav said:
Well, here we go...
This is not the way I wanted to post this thread, but fate was stronger than me
Guys, I spent last several months working on a stable Sense 4.1 base for our HD2. I succeeded in a lot of things. I got BT working. I got mic working in applications. I got this damn thing running smoother than my wife's Galaxy S3 (I'm not kidding)...
So, yesterday my HD2 died on me. For the second time. I can't afford to fix it anymore, I don't have neither time nor money for that. Mainly time... So, unfortunately, I have to stop the development right here.
Someone, please take it from here. It would be a real pity for me if this ROM died together with my HD2.
Here's the link. Enjoy.
http://d-h.st/7MZ
Disclaimer:
Frankly, I don't even know if it boots the way it is now. I was in the middle of something when this happened. Most probably, it will just work though.
Technical details:
Config: Data on Ext, DB on NAND, looped over EXT2. Yeah, it's returded fast.
System: mostly taken from other Sense 4.1 devices, proprietary files taken from several half-working Sense 4.x ROMs flying around here. Sound system taken from EvoHD2 ROM (yeah, CM9). Credits to Mr Evil for these files.
Kernel: Dorimanx 7.2 HWA (credits to Dori please)
Framework: stock Desire X ROM as a base, heavily modified to work with CM9 sound system, heavily optimized for smoothness.
NOTE for DEVs:
I was stunned to discover that DISABLING HW acceleration makes scrolling silky-smooth in 99% of the applications. Exceptions are: Rosie, Browser and... uh... that's it, I think. So, I REVERSED the way framework enables HW acceleration. Here's how: if the application doesn't request HW acceleration, it doesn't get it by default. If it requests it (HWAcceleration=true in the manifest), it DOESN'T get it either. If hwAcceleration=false in manifest, it DOES get it. This way, I only had to modify Rosie and the Browser and set hwAcceleration=false for them to actually GET the acceleration. The other apps just denied the acceleration natively. Please be aware of this change
Sense: stock Desire X ROM. I've got permission to use MyOne ROM (see Desire X forum), it has full 3D effects enabled and runs smooth as silk on HD2 (it's pretty damn smooth even with live wallpapers!)
What should work:
Everything. I know that WiFi router doesn't work, but that's it, more or less. Video shooting works at 15FPS. Sound recording works. Voice input works. BT works.
Known problems:
It does crash from time to time. Needs more work on system files. I was planning to recompile gralloc from CM9 to use it here, but didn't have the privilege to finish that.
For EXT2 loop to work, one needs to add creation of an empty data.img file in /Data/Data folder. Make it as big as possible. Format it for Ext2. The rest will be done by init.rc
............. Well, that's it. I'll be watching this thread. Don't ask me to develop anything though, I can't do anything without a working HD2. Sorry guys and good luck to anyone who will take it from here.
Bye
Click to expand...
Click to collapse
wow, nice job!
blackphoenix50 said:
I did all these but still cant install.....tried also with twrp it gave me an error about updater binary...i searched at google and i think that the problem is the updater-script file...could someone plz check it cz i dont have the knowledge for that....
Click to expand...
Click to collapse
There are a few double brackets in there. Mike_1996 noticed a few in this thread http://forum.xda-developers.com/showthread.php?t=2694879 thanks Mike. I spotted a couple more.
https://dl.dropboxusercontent.com/u/24033707/updater-script
Not tried this yet but looking forward to it, sad news about phone though, thanks.
updater-script modified http://www.mediafire.com/download/q8wt2wlh8aaokf8/updater-script.zip
modified with notepad++
now boot fine but take a long time !
i have installed with 5/40/5 partition clk 1.5 and ext4 2100 mb.
wifi don't work for me
bluetooth also
and comcorder
http://www.mediafire.com/download/zu1sz8u4qz7vwdr/commonsense4.1.zip
an image !
philipped346 said:
updater-script modified http://www.mediafire.com/download/q8wt2wlh8aaokf8/updater-script.zip
modified with notepad++
now boot fine but take a long time !
i have installed with 5/40/5 partition clk 1.5 and ext4 2100 mb.
wifi don't work for me
bluetooth also
and comcorder
http://www.mediafire.com/download/zu1sz8u4qz7vwdr/commonsense4.1.zip
Click to expand...
Click to collapse
does the recent apps appear when you long press the home button?cz i think its an essential feature...
I would just remove menu button and assign that to recent apps. that is the modern way. (not Samsung dinosasur way )
For system crash could be kernel fault... I remember when I tested dorimanx kernel each release was never really 100% stable independently from clock frequencies.
II test this rom of dungphp with tytung kernel (thank to all) and this is the same with sense 4.1 .
wifi/3g , camera , bluetooth , sound work .
camcorder don't work and google play work with uptades but can't instal news applications.(fixed instal apk
)
it's a very smooth rom and if someone can fix this problems .
View attachment 2656090
View attachment 2656091
this the link of one s ics2ville:removed
I have installed system on nand with dataonext (initrd intégrated) 5/370/5 :silly:
I have updated Google play in new installation and now it's OK.
new link http://www.mediafire.com/download/c8ds4r7g7qd7n5e/one_s_ics.zip
zenida said:
For system crash could be kernel fault... I remember when I tested dorimanx kernel each release was never really 100% stable independently from clock frequencies.
Click to expand...
Click to collapse
Dorimanx's kernel haven't given me one single problem with this ROM.
I used it as my daily driver until my HD2 died...
zenida said:
I have installed system on nand with dataonext (initrd intégrated) 5/370/5 :silly:
I have updated Google play in new installation and now it's OK.
new link http://www.mediafire.com/download/c8ds4r7g7qd7n5e/one_s_ics.zip
Click to expand...
Click to collapse
if you're using my ROM (I couldn't figure this out from your post), and use my initrd, then you have to make your system partition as SMALL as possible. Most of system files are relocated to EXT4.
For camcorder to work, copy it from any CM9 ROM.
Sense camcorder tries to record at 30FPS, which doesn't work with this version of stagefright. CM9 camcorder records at 15FPS and works flawlessly
thelonewolf_pav said:
if you're using my ROM (I couldn't figure this out from your post), and use my initrd, then you have to make your system partition as SMALL as possible. Most of system files are relocated to EXT4.
For camcorder to work, copy it from any CM9 ROM.
Sense camcorder tries to record at 30FPS, which doesn't work with this version of stagefright. CM9 camcorder records at 15FPS and works flawlessly
Click to expand...
Click to collapse
your rom is very smooth but i can't have wifi/3g working , it's a problem
philipped346 said:
your rom is very smooth but i can't have wifi/3g working , it's a problem
Click to expand...
Click to collapse
this is really strange. I had wifi and 3g working without any problems. I use both of them daily...
are you using magldr or clk?
what's your system size?
did you look at the logcat?
I use clk 1.5 and système size 5/40/5 .
Sent from my Nexus 5 using XDA Premium 4 mobile app
philipped346 said:
I use clk 1.5 and système size 5/40/5 .
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
interesting.
can you use ADB? if yes, try to:
cd /data
chmod -R 777 data
chmod -R 777 system
let me know if that changes anything
I test tomorow now i watch football .
Sent from my Nexus 5 using XDA Premium 4 mobile app