yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] Mucky2:
screenshots please? :o
[One (M7) Android Development] Ryche666:
There have been some screen shots taken already?
[One (M7) Android Development] kansasboy001:
Sprint version works great!

---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------

LS has an unnofical Tinted System Bars (DSB ) that Ryche66 has cherry picked into his ROM. He is uploading now.
[One (M7) Android Development] Ryche666:
It works great for m7ul and i hope to here feed back from you to make sure m7sprint is going just as well.

Working to get the Torch tile back. If anyone else has requests please keep me posted. I will also take a look into this Xceed kernel that people keep talking about. I am trying to make this smooth and as up to date as possible. I fear if i use a custom kernel i will be subject to there updates. I am going to do a test build with 4.9gcc rom and 4.8gcc kernel. I know it worked last winter after a lot of headache but i do believe it will go even smoother than the rom is going now
[One (M7) Android Development] ANDR01DN00B:
Does this beast have the CM Theme Engine?

Thanks
[One (M7) Android Development] Ryche666:
I haven't ran CM since 4.3 so I couldn't tell you:/
[One (M7) Android Development] kansasboy001:
Yes this has the cm theme engine.
[One (M7) Android Development] kansasboy001:
Sprint build with Tinted System Bars works Great!

If you want even better performance Slippery Sloth kernel from here: http://xdaforums.com/sprint-htc-one/development/kernel-nocturnals-slippery-slothaosp-4-t2859624

---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------

Sprint rom now has it's own thread located here:

http://xdaforums.com/sprint-htc-one/development/rom-kitkat-liquidsmooth-m7spr-homebrews-t2926735
[One (M7) Android Development] kma_29:
Can this be dirty flashed over the original Liquid Smooth?
[One (M7) Android Development] Ryche666:
Newer. Updates. Different kernel. Different device tree. More things work.

let's put a Margarita in this conversation.
[One (M7) Android Development] Ryche666:
No! This is too different.

let's put a Margarita in this conversation.
[One (M7) Android Development] ANDR01DN00B:
So I got a random reboot during a call... Stock kernel no modifications, really.
[One (M7) Android Development] Ryche666:
I don't know man. I been using this kernel, device tree, for nearly 8 months. I ported over to ls 2 weeks ago. It hasn't rebooted on me. It did once but it turned out I was playing angry birds in my pocket and the battery died:/ but the commits I have haven't changed since 4.3.
[One (M7) Android Development] Ryche666:
I know when I was using my work around for twrp because I refused to upgrade it and I was getting random reboots due to that. When I originally ported over and flashed it over the top of Official LS I got a few FC's. But I felt it would be expected since Official LS kernel looked like CM's kernel from last December. This kernel is a lot closer to cms and has all the patches cm has up to last monday
[One (M7) Android Development] Hollyca:
[MENTION=4965436]Ryche666[/MENTION]

Hey, thanks for this amazing rom ! Just one issue so far (big issue) it seems that your rom with Xceed Kernel disable apn and can't find any provider ...

Thanks, Hollyca
[One (M7) Android Development] Ryche666:
Probably. I haven't got to the Xceed kernel part yet. It might be AOSP based since the kernel use to be but now it's similar to CM's. I'm working on fixing the FM radio now and will hopefully get to the Xceed kernel but I want the problems fixed first before diving into more
[One (M7) Android Development] kansasboy001:
Kari, the dev of xceed kernel is also working on it.
[One (M7) Android Development] burgess_boy:
I have had this problem on all of the AOSP based roms so far and was wondering if anyone could provide some assistance.

Whenever I reboot my phone I can't get any signal - I lose all my apn list as well as the function of not being able to add any new apn settings. I also have "unknown" as my IMEI and Firmware under settings. I have tried flashing a Google Edition compatible radio to see if this works but nothing happens. The only fix is for me to flash the rom again.

I was wondering if this is a firmware issue? Would possibly flashing the Goggle Edition RUU fix this
[One (M7) Android Development] Ryche666:
I've gotten errors before due to the not updating twrp/cwm and the meta-inf that was used for the zip either it a rom or radio zip. I was cheating and using an old meta-inf file and copied it over to the new zip i was using. But as of lately since i flashed the latest twrp, radio, and hboot. I haven't had the cell or loss of apn. Doesn't mean i fixed it but it does mean i haven't had it since late August when i upgraded everything to the latest stable. It could be worth a shot since twrp and HTC put these updates out for a reason?
[One (M7) Android Development] Ryche666:
I spoke with the Xceed kernel man and he said he will take a look and see what he can do to port over his rom and hopefully get it stock and maintained with the latest CM nightlies and Xceed goodies(:
[One (M7) Android Development] burgess_boy:
Updating to latest recovery has fixed the problem.

EDIT: Hasn't fixed it also get bootloops and have to flash rom again to fix. I will try flashing latest firmware, hboot and radio tonight to see if it fixes anything.

Out of interest what hboot, firmware, radio are you running?
[One (M7) Android Development] Hollyca:
[MENTION=4965436]Ryche666[/MENTION]

Thanks for the answer, hope the xceed kernel will work soon with your rom

Hollyca
[One (M7) Android Development] santod040:
WRONG

FYI:

The last build I posted for LS, included the latest CM based msm8960 kernel sources as of the day of compilation.

Not sure where you get this thought that it was from last December, but that couldn't be further from true.

As far as the tinted status bar stuff, that was just added to LS within the last few weeks and isn't something anyone in this thread cherry-picked to make work.

We have added a new maintainer which has helped get that added.

I had intended on posting a 3.2 Milestone build with that new feature, but it seems other folks are trying to take this under their own belts and take credit for it anyways.

But let's not stretch truths or try and make my existing Official builds sound as if they were something other then what they were.

They included current sources at time of compile, kernel was stable, no reboots, and worked on all carriers.
[One (M7) Android Development] omaramiromo:
So, sir when the official liquidsmooth milestone 3.2 will available.. cant wait to try the official one.
[One (M7) Android Development] Ryche666:
Its exactly the same as the 11/2/14. The only difference is it is called milestone.3.2. But I'll post it if you want
[One (M7) Android Development] Mucky2:
When you'll upload a new build master? :o
[One (M7) Android Development] Ryche666:
I'll upload the milestone 3.2 tonight. There hasn't been any changes and I still haven't been able to find out what is causing the Sprint issue and the Torch Tile from not working:/ I'm tinkering with proprietaries right now on my own test builds in hopes to get the best of both AOKP and CM but I lose one thing to gain another:/
[One (M7) Android Development] Mucky2:
Nice ! I hope you're able to fix the bugs! You just need a coffee :P
[One (M7) Android Development] Ryche666:
Im not saying it is out dated by any means sir. I give it up to the maintainer and official builds. I was just explaining that LS m7 device looks the same folder and structure style as it did in december when i last used it and before CM and AOKP changed the structure and folder layout. But i have been more AOKP ever since i spent the time to port m7 ls kitkat last winter to just find out ART didnt work at the time:/
[One (M7) Android Development] santod040:
Not even close to being the same as it was a year ago...

There was no unified tree at that time even.

I'm not sure what you are trying to accomplish here or imply.

All I see is a user compiled version of LS with an odd device tree and borrowed kernel code.

Not much point in my opinion, rather see a kernel posted by itself, then another Liquid thread, of which I see you have posted two just recently in the One Dev section.

I guess I just don't quite understand the point, but to each his own.

I compiled builds when there were enough changes to make it worthwhile and when I knew the main base was in a stable state.

I am not one to compile each time 2 changes are made or bug fixes which have no effect on the m7.

Plus I have a job, multiple devices and roms which I maintain, and not a lot of active users in the m7_ul thread, so I don't exactly knock myself out to compile on a daily basis.

As I said a few posts back, I would post an official milestone build, and a user asked me when, so again, not sure why you are acting as if you are the party in control of that.

Doesn't exactly make a guy wanna spend his time keeping a device/tree/sources updated when others come along, claim they aren't and then post builds using others hard work.

You also mentioned in this thread that yours "looks" different due to your device tree.

The device tree isn't gonna change a lick of what the rom looks like...
[One (M7) Android Development] Ryche666:
Sir I made this thread and you are posting on my thread. It has a different look due to the device and kernel because of the hard work done by aicp and me updating daily and speaking with doc and devor of aicp on the daily to work out bugs. We have made it to out liking with a diff dpi, logo2menu, sound mods, and a simple but settle mods to the kernel. He asked when I will post the milestone but as I stated the only difference was that I cherry picked the transparent status bar and built the day before it was merged and milestone came out. These are homebrews and what I like and from AICP who I follow, keep in contact, and have spoke to before I posted my ported homebrews. Last winter when I successfully ported ls and got approval from ls to post it on xda I got stuck in Montana for work. Maintain and do your thing or whatever. I posted this to get ideas and try to progress my understanding and the extremes and possibilities of android. I am here on xda to help, give advice and ask for advice as I feel is the true reason why we give our source codes and have forums for q & a
[One (M7) Android Development] santod040:
Yeah, I am posting in your thread.

Public forum...

This thread of yours lacks any credits in the OP to LiquidSmooth team, me or anyone but yourself.

What you got permission for last winter has nothing to do with this winter.

If you had asked myself or any other members of the current LS Team, we would have gladly told you that we have official builds for the m7 and do not need 1 or 500 unofficial variations floating about.

It does not look any different...

DPI was already changeable in Settings within the rom.

Logo2menu is a kernel mod, not a rom modification, of which I have posted several versions with that feature for those that wanted it.

Sounds to me the only real change you've made was a minor sound hack.

I really don't agree that you have made it your own in any way or that it justifies it's own thread here on XDA.

But I am done with discussing this matter with you, so don't worry.
[One (M7) Android Development] Ryche666:
Thank you sir and to clarify the whole team this winter didn't give me permission. Only the OWNER of Liquidsmooth Google+ did the day before I opened this thread. I do believe his exact words were. I don't care if you post unofficial builds. So maybe he does like the diversity and openness to options?
[One (M7) Android Development] santod040:
Doesn't matter what anyone said a year ago, especially just the G+ community page owner.

Pretty sure there was no official m7 builds at that time and owner of G+ page has since changed.

Would be wise, in my opinion, to check with the devices current official maintainer.
[One (M7) Android Development] pandaball:
Thread reopened.
[One (M7) Android Development] Ryche666:
Thank you for reopening my thread!
[One (M7) Android Development] Ryche666:
MILESTONE 3.2 uploaded!

Enjoy everybody
[One (M7) Android Development] kravguy:
Where?
[One (M7) Android Development] Ryche666:
The download link. The opening post.
[One (M7) Android Development] kravguy:
That was weird. When a opened the link with the drive app, it wasn't there but opening through the browser worked. Thanks.
[Moto E Q&A, Help & Troubleshooting] mrasrii:
excuse me. sorry for my problem. i need solution :(

I found a strange thing on the motto E.

before I use the motto E, I use samsung ace3,

I usually at home using internet via a virtual miniport tethering from laptop

well the thing is, in my samsung work, being in the motto E connect (but i do not have an internet connection that way)

what's the solution?

i've already use stock rom, deodexed stock rom, CM11, AOSPA but still not influence

I've config IP and DNS. But still not the way.

note: Miniport and Modem and runs smoothly on samsung ace3 the internet connection and can range 200kb / s-400kb / s, while the motto E indicator dropped-down and down from the first connect 48KB / s to stabilize at 0KB / s.
[Xperia Z2 Q&A, Help & Troubleshooting] benjmiester:
Am I supposed to be wiping system, data, dalvik, and cache. Some Roms seem to say only wipe data and cache. I had been having problems with my cell data when trying non stock Roms so I thought I should double check the proper flashing process...

Rooted D6503 with unlocked BL too if that helps.
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
1. Download Flashtool

2. download a FTF

3. use flashtool to flash the FTF you downloaded

(ask if i need to elaborate)

4. Restore your TA if backed up (it will relock your bootloader)
[Xperia Z2 Q&A, Help & Troubleshooting] benjmiester:
Is this the process to restore to stock? or how I should be flashing all roms. I have recovery already running, so I had been flashing that way. I did back up my TA before I unlocked though, luckily. But I have D6503_17.1.2.A.0.314_Generic CA.ftf and flashtool installed standing by if that's what you would recommend. (From this thread: http://xdaforums.com/showthread.php?t=2759934)

I'm currently on this ROM : http://xdaforums.com/showthread.php?t=2755390 With Doom Kernel, twrp boots fine from it.

And data and wifi both work perfectly fine for me, but as I mentioned in the other thread, any non-stock rom breaks the data until I restart. Then if I use wifi, data is broken after working, until I restart. So you're recommending going back to stock with FTF, and retoring TA, and then trying it all again?
[General Questions and Answers] juan120535:
Anybody that has the ktoonsez kernel for the Galaxy S5, have you had trouble with the voltages for the CPU. My phone keeps restarting after a while of using it with the voltage settings it's set at.
[Xperia Z2 Q&A, Help & Troubleshooting] sathomps:
I'm in CWM, and I can't sideload because it says "error: device not found". Running "adb devices" shows nothing. I see that Xperia Z2 is not recognized (yellow exclamation point) in device management.

The Google USB drivers aren't recognized. The Google USB drivers with the updated android_winusb.inf I downloaded from Sony in order to fastboot aren't recognized. The Xperia Z2 drivers I got from Sony aren't recognized.

So, could anyone please tell me where I could get some drivers so I can sideload this POS? Or does anyone have any other ideas for why I can't sideload?

I already tried searching for answers and drivers, and checking the sticky, but nobody else seems to be having this problem. Thanks much.

PS: I can't use my sdcard because my sdcard to usb dongle thing just broke. I can't download the zip I need directly onto the phone because it won't boot as is.
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
Try flashing TWRP, For some reason the CWM drivers for any Xperia just doesnt exist.

TWRP though on the other hand works perfectly fine after you insall the drivers

you can use flashtool to flash TWRP If you have a unlocked bootloader which im asuming you have?
[Xperia Z2 Q&A, Help & Troubleshooting] sathomps:
Yeah, I've unlocked the bootloader. I'll give TWRP a shot, then. It's weird that CWM drivers don't exist. Thanks.
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
they havent been avaliable for Xperias for a while, i found i had little issues using TWRP simply because i could even connect my Z2 to my PC in MTP mode whilst in TWRP
[LG Optimus G Pro] sbacham:
Im using indian g pro (E988),can i flash stock f240 rom??? Or any problems?
[XDA Assist] vikichet:
Pls help i need flash img of custom rom for Micromax A35

I tried to re flash recovery mode but still m stuckd at boot logo
[XDA Assist] :
Hi,

Unfortunately there's no section for your device on XDA. Asking here for help would be best,

> Android Development and Hacking > Android Q&A, Help & Troubleshooting

You may want to be more specific when you post there. Like what exactly you tried to flash, and which version of the a35 you have.

Good luck!

---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------

You could see if this thread helps also,

> Android Development and Hacking > Android General > Ultimate unbricking guide for micromax a35
[Upgrading, Modifying and Unlocking] bugmenot:
is there such a thing as a genetic aku for pocket pc phones? I would really like to get the AKU 3.3 or 3.5 installed, but you see I have a palm 700w and there is no palm update to this. So is there a genetic aku 3.3 or 3.5 I can use on my device? Thank you.
[Upgrading, Modifying and Unlocking] bugmenot:
anyone please?
[Upgrading, Modifying and Unlocking] klavier:
yeah this is a good question
[Upgrading, Modifying and Unlocking] xplode:
there is no genetic stuff in pocketpc's yes maybe after 50 years, there is no generic AKU yet, maybe there will be for WM6 and will be distributed as update trough windowsupdate. The only way for you guys to get latest AKU's is to port them from another device, like all the others.
[Upgrading, Modifying and Unlocking] bugmenot:
Oh okay. So is there anyone willing to do this? Please?
[Upgrading, Modifying and Unlocking] bugmenot:
bump please?
[Upgrading, Modifying and Unlocking] klavier:
anyone please help us?
[Upgrading, Modifying and Unlocking] Rudegar:
one needs the device in question

one needs alot! of time maybe 50 manhours

one needs alot of enery

and one could still fail ...

you can keep bumbing this thread on start to get involed yourself
[Upgrading, Modifying and Unlocking] bugmenot:
well I thought maybe someone could take aku3.5 from their device and take out everything specific to that phone that won't work on another phone and there we go?
[Upgrading, Modifying and Unlocking] Rudegar:
roms only have the drivers spc for the hardware for the device it was made for

so removing the hardware spc stuff mean a rom without any drivers and then it's uselss
[Upgrading, Modifying and Unlocking] bugmenot:
there is no way to make a rom genetic and then add the hardware specific stuff from WM5 to it? Or add wm6 genetic ontop of wm5 like an upgrade isntall or what not?
[Upgrading, Modifying and Unlocking] klavier:
palm just announced that the 750 will get an upgrade wait till then so someone can get the rom and port it to the 700
[Upgrading, Modifying and Unlocking] Rudegar:
"there is no way to make a rom genetic and then add the hardware specific stuff from WM5 to it? Or add wm6 genetic ontop of wm5 like an upgrade isntall or what not?"

yeah i belive it is possible

but it's very hard to do and it have to don spc for each device

taking along time to do

and it means that it's not generic
[Upgrading, Modifying and Unlocking] bugmenot:
well i guess the one from the treo 750 could be edited to work for the 700, i guess?
[Huawei MediaPad, T-Mobile SpringBoard] potatohead:
Below is the latest Huawei Official KItaKat Beta for 7D-501u (3G Mediapad X1 aka Honor X1 in China).

Main characteristics of this ROM are 320DPI and a whopping 1.4-1.5GB of free memory after boot.

Initial feedback by Chinese users is positive.

YMMV

http://update.hicloud.com:8180/TDS/...g0/v15243/f2/full/7D-501uV100R002C553B001.zip

If you encounter problems running this beta, 'fraid not, just download the latest official 501u ROMs from Huawei and flash it back.

JB 4.2.2 / EMUI 2.0 / 320DPI - http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI2.0_Android 4.2_V100R001C233B021.zip&rid=771

KK 4.4.2 / EMUI 2.3 / 400DPI (Xposed 2.5.1 works empowering you with the ability to set per app DPI) - http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.3_V100R002C233B010.zip&rid=592
[Huawei MediaPad, T-Mobile SpringBoard] realeze:
Is it even possible to flash 501U ROM onto 503L?
[Huawei MediaPad, T-Mobile SpringBoard] potatohead:
Sorry, my bad, i copied some of the contents from my 503L thread, already corrected the mistake (the links were the correct 501u ROMs though).

To answer your qn, it is possible to flash 501u ROM onto 503L, but that would be pointless as LTE will almost certainly not work.
[Huawei MediaPad, T-Mobile SpringBoard] bthoven:
Anyone has tried this rom? Really need feedback before jumping in.

Does it come with google play and other necessary google stuff?
[Huawei MediaPad, T-Mobile SpringBoard] potatohead:
definitely no google services 'pre-installed' in China ROMs (all the 3 above are China ROMs).

u can however 'wake' them up by removing /cust/channel/XXX_XX_XX/xml/UNSTALL_APK.XML (/XXX_XX_XX is the only folder inside /channel; its name may vary from ROM to ROM)

will update the thread if i can find international version of 501u ROMs.
[Huawei MediaPad, T-Mobile SpringBoard] vuhongduong:
I successfully flashed it at the second time with another bigger rom download.

I can say that it is not worth of flashing because font size is very small and chrome is not compatible totally with phone page.

So, I decided to flash back to C233B010.

Don't waist your time.
[Huawei MediaPad, T-Mobile SpringBoard] bthoven:
any good for this rom? I'm running the 4.4.2 400dpi imui 3.0 which has two annoying issues:

1. can't set Nova Launcher as a default launcher

2. it is mobile UI, not tablet-optimized ui as in official 4.2.2 imui 2.0.

Does it has the above two issues?

How is it different from the 400dpi one? (already root, solve the google+ things).
[Huawei MediaPad, T-Mobile SpringBoard] bthoven:
Hi,

I'm running the 4.4.2 emui 3.0 400dpi from the below xda post:

http://xdaforums.com/huawei-mediapad/general/rom-kitkat-4-4-2-emui-3-0-400-dpi-t2925015

rooted it with iroot, solved the google+ compatibility as suggested in this board, now all incompatible apps are compatible.

My only problem is I hate the mobile UI on this 400dpi rom (prefer the tablet UI as in the official rom b020/b021, or, I guess, on any 320dpi rom).

I intend to update the rom to the one post here (320dpi). I've tried several times without success. It recogized my update file and after it spent some time loading the file on the updating display, it reported failed every time. What I did was creating dload folder, put the update.app into it with some other small files I brought from this 400dpi upgrade; or from other roms.

I also downloaded and tried updating with the official kitkat 400dpi (international rom, B102) from Huawei Germany website, it also failed at the same point (the display which has big EMUI banner)

I tried both on 32gb class 10, and 4gb class 4 microsd card.

Anyone had experience in updating your X1 (7D-501u) from 400dpi to 320dpi? What small files you put inside and outside dload folder (please share those files)? Any tips would be really appreciated.