yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] Putra:
Indonesian carriers

First, thank u XdaJoJo & Toenailed & Sin & the other gurus for their excellent work. They all have made our Xda's so much better. I've been following JoJo's thread and I must say there are very few people like him who would take the time to answer almost every request. Thank u guys! :D :D :D

For the carriers, I have a very simple solution. I used this method the 1st time I upgraded to SE with Sin's merged ROM. Before the upgrade, I saved my old (2003) EXTROM files to my PC. You should see the carrier files regardless if you're in UK, S'pore or Indo or wherever. And also the autoconfig.txt file. After upgrading to SE (regardless if it's JoJo's version, or Sin's or anyone else's), just copy back the autoconfig.txt file to the EXTROM and the other cabs like satelindo.cab, telkomsel.cab & the O2Asia**.cab. I deleted Sin's Aust carrier files, and even edited my autoconfig.txt so that it only gives me only satelindo, telkomsel or starhub (the others I don't use). I also deleted the other cabs and saved a lot of space in my EXTROM.

This is a very simple method which anyone can follow.

Now, we can leave the experts like JoJo, Buzz & the others in peace to tinker with Magneto, right? :wink:
[MDA II, XDA II, 2060 ROM Development] rhmartin:
Gotong Royong

Very well said Putra.

I think forum members here from Indonesia should carry on and help out each other: experts, novice, newbies & non-techies. Communicating using the local bahasa may help, see the Philippine Version forum ..... we even use provincial dialects to communicate. :lol:

Benar-benar saya setuju dengan Putra bahwa kita lebih membutuhkan Jojo, Buzz & Toe untuk membantu perbaiki versi Magneto di XDA II!!!

Salam semua. (to Jojo: ibig sabihin nito: regards to all)
[MDA II, XDA II, 2060 ROM Development] trussing:
hi guys.. im a new xdaII user!.. hello all.. btw, is there any chance for me to upgrade the cleartype setting only? without upgrading to WM2K3SE? just wanna make my fonts smaller.. thanks!
[MDA II, XDA II, 2060 ROM Development] Phreakazoidz:
u can make ur font smaller

try Start - setting - systems - screen - text Size

Thanks

Phreakazoidz
[MDA II, XDA II, 2060 ROM Development] trussing:
cleartype version WM2K3 for WM2K2

thanks Phreakazoidz.. but i dont think theres a font setting like "text size" in WM2002.. (im not thinking to upgrad to WM2K3 yet..) My version XDAII is original with ROM 1.66.00WWE.. i havent upgrade since i bought it.. btw thanbks 4 your respon..

btw, boleh add yahoo anda gak? i need to talk about upgrading to WM2K3.. masih takut kalo ada masalah.. thanks again..
[MDA II, XDA II, 2060 ROM Development] Phreakazoidz:
Ok

No Problem My. Id Phreakazoidz

thanks
[MDA II, XDA II, 2060 ROM Development] xda2jojo:
Customized for Indonesia

ROM 2.06.00 Xda2.HERY.mod

Halo kepada semua teman saya dari Indonesia
[MDA II, XDA II, 2060 ROM Development] c_shekhar:
Xda2JoJo.v3.2zS customised for INDIA

Dear wizards can any onyone tell whether Xda2JoJo.v3.2zS customised for INDIA also available?.....chandra shekhar
[MDA II, XDA II, 2060 ROM Development] nDOET:
File not found

there's nothing file or dir..

where can i get the file ?
[MDA II, XDA II, 2060 ROM Development] bagoesdonny:
Broken/Invalid Link

:confused: I can't open the that you gave... Appear message Alert 550 Failed to change directory. Can you solve this problem? Thanks bro...
[MDA II, XDA II, 2060 ROM Development] kangodoy:
File is nothing

I do not found file on this ftp://ftp.xda-developers.com/SmartG...oJo.v3.2zS.IndonCustomizedTelkomselSatelindo/

Hm..., i wanna try it, Please help me
[One (M7) Q&A, Help & Troubleshooting] iflip:
Currently I'm not an htc owner but my introduction to Android was through htc phones. Htc one looks amazing. Ive grown to like the stock Android aosp experience because of its overall speed and performance. But do like some of the add ons that some phone manufacturers have implemented.

If I owned a one I'd probably go with a debloated sense with nova launcher.

But Now that the Google editions Roms are out what have you grown to like better?
[One (M7) Q&A, Help & Troubleshooting] postfatal:
Try them both and see which one you prefer. Our opinions are totally irrelevant when it comes to what you prefer.
[One (M7) Q&A, Help & Troubleshooting] CheesyNutz:
THIS ^^^^^^^^^^^^^
[One (M7) Q&A, Help & Troubleshooting] iflip:
I stated that I currently do not own an htc device yet so your opinions are totally relevant at the moment.
[One (M7) Q&A, Help & Troubleshooting] redbull123:
They aren't relevant at all..

There are enough youtube videos of both roms for you to make your own mind up. Just get the phone, use sense for a couple of days, then use a GE rom for a couple of days and see which one you prefer.
[One (M7) Q&A, Help & Troubleshooting] jotha:
All necessary said. There is no "best" or "better" in roms. Only personal preferences. So try yourself and decide.
[Fascinate Q&A, Help & Troubleshooting] CrackBurglar:
So I had CM 7.1 on my wife's fascinate for close to 7 months. I wanted to return it to stock. But I could not ever get the samsung drivers and Odin to see the phone. I have multiple OEM fascinate data cables. I've tried the whole schpeel on XP vista 32 & 64, win7 32 & 64, Win8 -64... All no go.

It leads me to believe it is the usb port on the device. I've adjusted it. Cleaned it. inspected it. Cleaned it some more...

The only thing I've been able to do is flash (via CWR) the Glitch Kernel, and flash CM 7.2

I'm happy with cm 7.2 w/exception of not having the play store on the device.

Is there nothing more I could do with this device to regain usb connectivity.

When I plug the cable, it charges the battery. that is about all.

Thoughts?

Thanks!
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
I don't know how to help you with Odin and the USB situation, but if you want the Google Apps (Play Store, Talk, etc.) you can get them onto your SD card with a microSD to regular SD adapter (probably really cheap on Amazon, and they come with most microSD cards in retail) and a card reader for your computer. Take out the microSD card from the phone, put it in the adapter, download the Gapps package from goo.im's gapps page, and put it on the SD card. Gapps is flashed with ClockWorkMod.

Actually, I had trouble getting my phone back to stock, and at the moment i am on stock 2.3.5, but I actually used a USB cable from a GS4 and it worked just fine (my OEM fascinate cable doesn't comply with Odin usually).
[Galaxy Note II Q&A, Help & Troubleshooting] chokxxi90210:
Hi All, I bought a new Car Bluetooth Handsfree Kit from Blaupunkt few days back.

Now my Note 2 does pair with the BT Device for both Media & Phone function; but when i call someone or receive a call using the BT Handsfree, I am able to hear the other person but the other person is not able to hear my voice...!!! Its like I am on mute..!!

I tested the same BT Handsfree with my wife's Sony Xperia ZR and it functions perfect with it.

Is there any way i can make my GN2 work fine with the BT Handsfree ?? Please help me out guys....

I have tried pairing & re-pairing but still same thing is happening. Is this common ??

Please help me guys....
[Sprint HTC One (M7)] sup3rg0d:
I was wondering if anyone here on Sense ROM got USB Tethering to work? I had this working on CM10.1 default but it does not seem to turn on with Sense ROM on sprint.
[One (M7) Original Android Development] TripNRaVeR:
​

TripNDroid Mobile Engineering is proud to hereby announce the release of the TripNDroid rom for the HTC M7 also known as the HTC One

Working:

- Mobile network (data, calls, sms etc.)

- GPS

- Bluetooth

- Bluetooth tethering

- Wifi

- WIFI Hotspot

- Hardware video decoder

- Hardware acceleration (2D/3D)

- Audio

- MIC (recording)

- Camera (rear and front)

- Leds (incl. blink)

- NFC

A brand new ROM, still in early stages, completely rebuilded in Android 4.3.

Please report anything you find! :)

Since Android 4.3 the ROM will have its own style and with every release there will be new features, new looks etc. Eventually it will be a rom completely different from any other rom.

Features:

Display is 473x473 dpi!

Launcher3

First and only rom with native FFmpeg support

Up to 7.1 surround sound

Dolby DTS decoder

Custom ringtones

Custom messaging tones

Custom wallpapers

Kernel based thermal control

TDF support

Advanced powersaving mode

Custom Adreno drivers

Build with Linaro toolchain

Supported A/V Formats

- AC3, Dolby DTS, Dolby DTS-HD, MKV, WMV, WMA, MOV, REAL and more!

Use Quadrant for example to verify the DPI

Installation instructions:

- Go into recovery

- When coming from another rom do a full wipe

- Format /system

- Flash the rom

- Reboot

- Enjoy TripNDroid on the HTC One

Screenshot:

Major changes for 028:

- Added antibanding setting in camera app

- Enable skintone enhancement for camera

- Added 4.5mp picture size

- Update speaker configuration

- Volume wake fix

Other changes just check github!

Download rom:

http://trip.droidsrc.com/tripndroid_m7-ota-eng.noeri_028.zip

Download HD 1080P demo movies with Dolby audio for ffmpeg testing

City Redux demo with lossless Dolby TrueHD 7.1 audio

https://mega.co.nz/#!iMYARBoR!E7x0-QkR4GuGNyDFvWnAowC4BAlAo3C8xSiZZNUeGe8

LG Circle demo with Dolby Digital 5.1 audio

https://mega.co.nz/#!eJ5GUBzK!B6kkyztxNHE1L5VYIEY7YB4WD4dwShHTTuxguSqbX8o

LG Wild Faces demo with Dolby Digital 5.1 audio

https://mega.co.nz/#!jcZGySyb!VW1L6wcd3JBg2UBUJseunjQP-ENKI7n2Dn5e9V2lnJA

DONT INSTALL ADDITIONAL GAPPS PACKAGE ON THIS ROM

Sources:

https://github.com/TripNRaVeR

Do it yourself!

The complete tutorial how to build a TripNDroid rom

On ubuntu from the command line execute the following:

mkdir -p ~/bin
mkdir -p ~/android/system

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

chmod a+x ~/bin/repo

REBOOT

cd ~/android/system/

repo init -u git://github.com/TripNRaVeR/android.git -b master-43

. build/envsetup.sh

lunch

choose tripndroid-m7-userdebug

mka -j8 otapackage

Replace 8 with the number of CPU's in youre system

Credits:

CyanogenMod github

AOKP github

BinDroid for providing webspace

xxsashixx for providing webspace

TripNDroid Mobile Engineering (offline after hosting issues)

www.tripndroid.com
[One (M7) Original Android Development] gifton1:
Cheers Trip, great to have you here.
[One (M7) Original Android Development] DJW6927:
Oh yeah..how's this against the standard cm bugs please chef? eg. bluetooth in call audio?
[One (M7) Original Android Development] TripNRaVeR:
Well i have no clue what bugs are in the cm rom, and i dont have any bluetooth device. So cant give any proper answer:o
[One (M7) Original Android Development] DJW6927:
Downloading to test 1st thing in the morning.

Never mind Kate Middleton - here's Trip's new baby :)
[One (M7) Original Android Development] yeeson:
Using the Google Edition 2.14.1700.15 code?
[One (M7) Original Android Development] aamitabh28:
Really glad to have you here!

Loved your work on the one x !!!!
[One (M7) Original Android Development] law16:
Alright trip good to see u still building ROMs I was a big fan of your work with miui for the sensation cant wait to see what u bring us
[One (M7) Original Android Development] razer1224:
Glad to see you here

:)
[One (M7) Original Android Development] yeeson:
Cannot use GE's kernel！
[One (M7) Original Android Development] TripNRaVeR:
This is just partly based on GE.
[One (M7) Original Android Development] yeeson:
Thanks！
[One (M7) Original Android Development] nicksmizzle:
sweet, nice to have you here, haven't had you dev for a device i had since i owned the sensation :p
[One (M7) Original Android Development] raycaster3:
Initial feedback. Super snappy. I dig the customizations and seems to run really well.

Cpl observations:

Swipe in keyboard doesn't work (no biggie)

The backlight on the keys doesn't ever shut off. That kind of makes the rom unusable for me at the moment. I'll most def come back.

Sent from my HTC One
[One (M7) Original Android Development] kozmikkick:
Audio isn't working on handset when making calls. Same with speaker phone. Here is a logcat.

http://pastebin.com/Ef2dr9L2
[One (M7) Original Android Development] Magpir:
whats this? something new?
[One (M7) Original Android Development] reinierkramer:
I'm really happy you now have a htc one. Your cunstom roms for htc sensation were always very good!
[One (M7) Original Android Development] razer1224:
Flash PA GAPPS For the No Biggie
[One (M7) Original Android Development] KhanSW:
I couldn't agree more, glad to see you here. Loved the miui Rom on the sensation. It's good to see you were able to work things out with the xda staff. Welcome back!
[One (M7) Original Android Development] aamitabh28:
Will the kernel be released seperately too mate??
[One (M7) Original Android Development] formula84:
Well Done, I did this by hand because I am a n00b with Git still and doing a revert is beyond me. I need to do some reading :)
[One (M7) Original Android Development] superleeds27:
Did you do a build with this fix?
[One (M7) Original Android Development] formula84:
Yes + Proximity adjustments + lower vibration + IR Support, I have tested IR only by making sure the service is loaded and the app works and sends commands, yet to be determined if it works with a device yet (At work with nothing to test with)

I will upload my build when i get time later if anyone is interested.
[One (M7) Original Android Development] superleeds27:
Yeah please!
[One (M7) Original Android Development] formula84:
So IR is not working for me, realized we have a TV i could test with. I am running a clean build now to see if it makes a diff. If its not working I wonder what it could be because I triple checked everything...hopefully if a n00b can't get it to work, maybe TripNRaVeR, while he does not agree with adding to main build, perhaps he could lend a hand getting it to work for us "self builders"

Oh and the proximity adjustment has fixed my issue with the Automation Unlock/Lock app I use with my flipcase. Commit - https://github.com/CyanogenMod/andr...mmit/78d732b78152db6fb4db3fbfeafa6ee0f65ee069
[One (M7) Original Android Development] Alex740il:
I am total n00b at this.. How did you add proximity fix commit? What is the command and in what folder did you execute it??

New version 005 is working great so far! Feels like the battery drain is just a bit faster though...
[One (M7) Original Android Development] tnicko:
Is the camera working for you? Both Focal and AOSP camera still FC on me.
[One (M7) Original Android Development] TripNRaVeR:
They work, did you try full wipe before installing?

Something else:

Thinking about removing cm-profiles, anyone uses it? :confused:
[One (M7) Original Android Development] Alex740il:
Both works here, I dirty flashed.
[One (M7) Original Android Development] tnicko:
Yes, full wipe. Several times actually ;p

I'll try again. Thanks guys. I read a few post up at the top where folks said they were FC'ing on them as well. But then I read you were uploading a fix. Pretty sure that's the one I grabbed.
[One (M7) Original Android Development] formula84:
Was broken for me on the build Alex posted but v5 works fine for me on FFC using aosp camera and focal.
[One (M7) Original Android Development] tnicko:
Sorry guys. My bad. It was n3ocort3x's kernel that was the culprit. I was flashing it to fix the sound issue.

So what's everyone using to temporarily solve the audio issue?
[One (M7) Original Android Development] formula84:
Google Drive Direct link - tripndroid_m7-ota-eng.formula84.zip

Sync at 20130826 23:00 est

Has my minor proximity adjustment triggers at a further distance then before, TripNRaVeR committed the vibration lower default value, I also tried 3 different ways to get ir support functional and failed. I really hope TripNRaVeR can lend a hand, I think it's something with his kernel / ramdisk setup.
[One (M7) Original Android Development] formula84:
[MENTION=2689951]TripNRaVeR[/MENTION] Since you seem to be on the cutting edge of Sound / Graphics not sure if you have seen the Work [MENTION=1815755]intervigil[/MENTION] has been doing with TFA9887 here - https://github.com/intervigilium/android_device_htc_m7-common/commits/tfa9887 | https://github.com/intervigilium/proprietary_vendor_htc/commits/cm-10.2 | https://github.com/intervigilium/an...mmit/d2cd3ee74b6e1f7686726d98d1d3358611ebc3a1

Seems interesting.
[One (M7) Original Android Development] Alex740il:
Anything I post is build from source, but doesn't mean its complete. Most of the time its while [MENTION=2689951]TripNRaVeR[/MENTION] is in the middle of something, so not all code is updated and some things get borked. Always best to stick with his official releases in OP.
[One (M7) Original Android Development] tnicko:
So everyone is just waiting for the next release to get the audio back from the headphone jack? I saw that Trip was reverting the audio driver.
[One (M7) Original Android Development] TripNRaVeR:
Only the WCD driver update is reverted.
[One (M7) Original Android Development] formula84:
Check the build I just posted this morning its all working (a few posts up), fresh sync from last night @ 11pm EST
[One (M7) Original Android Development] tnicko:
Cool man. Thanks!

---------- Post added at 10:19 PM ---------- Previous post was at 10:15 PM ----------

Yes, this is the one I mean>

Revert "sound: update wcd9304 and wcd9310 codec"

I figured this is why we lost sound out of the headphone jack. So in reverting, I thought that would be the fix.
[One (M7) Original Android Development] TripNRaVeR:
Trying to get a fresh build up tonight.
[One (M7) Original Android Development] formula84:
That new touch driver fixed an issue I have always had with aosp on my m7...Thank you

Whenever I would use my thumb to scroll inside an email message it would treat it like a multi touch zoom in...

No longer happening, your great man keep it up, oh and let's not forget FFC works as it should finally. Your on a roll
[One (M7) Original Android Development] Alex740il:
You're doing an amazing job! Thank you!

Touch is fixed for me also, forgot to mention it...
[One (M7) Original Android Development] TripNRaVeR:
Version 006 has arrived :)

On to 007!
[One (M7) Original Android Development] formula84:
I have brought this up a few times, but do you think you could lend a hand in getting IR to work for self builders? I got everything done and still no go, I have a feeling its something in the ramdisk -> init.qcom.rc

All i ask is you look at what i have added and give a response on possible reasons why its not working, I verified all files and permissions are in place, so i think it has something to due with the kernel.

Question I have synced the CM kernel but not sure how to build your rom with the CM kernel instead to test if its kernel side or just in ramdisk, because my thought is even if I build with CM Kernel it would use your custom ramdisk and I would have my answer wether its kernel or ramdisk thats the problem.

Edit: Im a n00b but I just poked around and found under Device/htc/m7/boardconfig.mk

# Kernel building

TARGET_KERNEL_SOURCE := kernel/htc/m7

TARGET_KERNEL_CONFIG := tripndroid_m7_defconfig

So I can change this to the CM kernel and test my theory. But please still look over my question and let me know if you would entertain the idea of allowing me to submit what I changed and look it over for issues.

Edit 2: While comparing your ramdisk with CM i found something maybe in ueventd.qcom.rc

cm has = # cir /dev/ttyHSL2 0660 system system

you have=# cir /dev/ttyHSL3 0660 system system

all the others seem to match? maybe thats a potential culprit? (Please remember I am a n00b, and this is me guessing)

with the exception of missing

# keystore

/dev/qseecom 0660 system drmrpc

Not sure what this is or why it was removed, but maybe its worth mentioning, idk.
[One (M7) Original Android Development] TripNRaVeR:
I dont have any CIR firmware included in my work, so it will fail unless you add it. Later releases also have the CIR service and ramdisk support removed. Means that you also need to add them again.
[One (M7) Original Android Development] TripNRaVeR:
You have a post here with almost only issues in it. You can just diff my source against cm and add the stuff you guess is needed. There is a reason to make a custom rom, to get things differently... there could be up to 20 reasons why it doesnt work, but unless you know what youre doing and have time to read trough every commit and see what is removed and what not you aint gonna fix it. The fact that my source differs at many points is because its mostly my own work, other roms copy the cm source and start building.

But applying such patches directly from a cm or equivalent source will at over 90% of the cases never work. You always need to adjust them to my source, that is not really hard but time consuming and you just need to know what you need to edit.
[One (M7) Original Android Development] formula84:
While I appreciate you taking time to respond, I am not really getting anything from you of substance. Your really saying that out of everything I posted and took all that time to compare and do my uneducated logic on is useless to you? I thought with all that info you could easily make some suggestions at least, not the response I got.

My build with the CM Kernel using your ramdisk did not work, so its nothing in your kernel thats the problem which leaves only ramdisk IMO.

Can you at least look over what comments regarding ramdisk edits again please, its really only 3 adjustments... the rest is all plug and play easy stuff, the ramdisk stuff is whats puzzling to me as yours varies much from CM.

My main point here is I really like your Rom because I feel you have a better base (fixes + performance) and while I miss features from SlimBean and Carbon I want to stick with your Rom... While everything else to me besides IR is minor, i find IR really useful and thats why I have spent hours trying get your Rom to work with IR like majority of other AOSP roms out there, rather then just flash others and be done. I would rather learn and fix what i want to run personally.

I would greatly appreciate the smallest amount of help as I feel after all the communication I have put in you gave me back vague answers.

Like the below thing I have pointed out twice now with not a comment from you...why does this differ from all others and whats the change do?

Edit 2: While comparing your ramdisk with CM i found something maybe in ueventd.qcom.rc

cm has = # cir /dev/ttyHSL2 0660 system system

you have=# cir /dev/ttyHSL3 0660 system system
[One (M7) Original Android Development] tnicko:
Good **** man. Sound is working again ;) Only problem I have now is I'm unable to select, alter or delete the APN's. Long-pressing doesn't work, selecting the radio button off to the right will temporarily select the APN but then the selection will disappear. Strange.

Thanks for all your work man!
[One (M7) Original Android Development] xxsashixx:
One of the best roms I've used to date.

Couple of problems though

1. Capacitive Buttons Brightness, if I use this, the LEDs never turn off. Other roms don't have this problem.

2. Kernel doesn't ever deep sleep? The most is at 144Mhz, usually around 40% of the time, no partial wakelocks, there should be at least 1% deep sleep, however this is not the case. Again other roms don't have this problem using same apps/usage

3a. Any news for your stock kernel for UV & logo2menu?

3b. Tripndroid governor doesn't allow underclocking?

Thanks!
[One (M7) Original Android Development] TripNRaVeR:
The problem is that i cant give you the answer as i need to look into everything myself again. Most likely the problem is not even related to anything you posted. There are much much more bigger changes that all -could- cause a problem.
[One (M7) Original Android Development] Alex740il:
Looks like you changed the proximity sensor calibration value. This cause black screen for me. Could do nothing until the other end hung up. For what its worth, 0xFFFF3024 works for me. I set it using below command.. How can I make it survive reboot?

echo "0x0 0xFFFF3024" > /sys/devices/virtual/optical_sensors/proximity/ps_kadc