yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] Evaldas.:
Hello ladies and gentlemen. I've received a Kindle Fire from my cousins. As I was told they were trying to root their device, but failed to do it.

I've tried that 20sec hard reset thingy, it didn't worked at all.

All i get is KindleFire textlogo at boot.

Could you link me to the right direction fixing it? I had no problems with my samsung device, but I'm new at Kindle stuff.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
What precisely does the boot animation do? is it static and bright or are there changes from beginning to end? Post a youtube video of it let us see what it does. just to let you know a hard reset will do nothing to fix the issue.
[Kindle Fire Q&A, Help & Troubleshooting] Evaldas.:
All I get is this static logo, no animations.

Holding power button can just turn on/off device. Nothing else.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Could just be stuck in fastboot getting it out of is is another thing because I`m guessing you do not have the drivers installed on your pc. What operating system are you on?
[Galaxy S III Themes and Apps] m112:
Hello,

I flashed my sgs3 with Omega 27.2 rom. Everything looks ok so far however I would like to revert back to original TouchWizz green notification icons. I don't like the current blue theme.

Is there any way to achieve this?

Thanks
[Galaxy S III Themes and Apps] forwardroll:
Read the omega thread.
[HTC Desire S] badflife:
Hi I have following problem.

I am using Miui 4 2.9.29 and i can't use goggle voice. Altough it is installed.

But in play store there is no option to open the app or deinstall it.

I have posted some screen shoots below. I don't have this problems with other roms.

Thanks in advance.
[Nook Touch General] xdaolli:
Hi all:

I would like to use an App to control my Logitech Squeezeboxes via my rooted Nook. However, the App does not find my Squeezeboxes on my network. I did some testing and found the problem:

On my rooted Nook, the ports 9000 tcp and 3483 tcp/udp seem not to be open (as seen w/ a port scanner).

However, these ports are used to find & communicate w/ the squeezeboxes.

-> How can I get these ports opened on my Nook??

(Note: This is a Nook internal problem - it is not the router / firewall blocking these....)

Thanks for your help.

Heiner

P.S. I would have posted in the android dev section, but as a newbie, I am not allowed to.....
[Nook Touch General] xdaolli:
Does nobody have an answer to this?

Any help would be greatly appreciated....

Thanks, Heiner
[Nook Touch General] Renate:
Huh?

A port scanner looking at the open ports on the Nook is not going to show much except 5555 for ADB.

Are you saying that you can't connect to a 9000 port on a Logitech whatever-it-is from a Nook?

Are you using an app from Logitech or are you writing one?
[Nook Touch General] xdaolli:
Hi. Thanks for your feedback.

And yes: I can't connect to a 9000 port from the Nook.

(Also, I am using a Logitech App, which is not working.

There is a similar App form a 3rd party, which works. But I would like to use the Logitech one)

However, I don't understand your comment 'looking at the open port....'. Why should I see only 5555?

I also so 21 for FTP, but not the ports I need.

Again, I am a newbi, but that is exactly what I want:

Looking at port 9000 from the nook. To my understanding, that needs to be open on the Nook - and it isn't.

(On the other end - a Synology NAS, where the Logitech Squeezeboxserver is running, I can check the relevant ports and they are open.)

Any ideas?

Heiner
[Nook Touch General] roustabout:
If the 3rd party app works, almost certainly your NST is permitting traffic out on port 9000.

What Renata means is this: you are on a PC trying to connect to 9000 on the NST. Nothing is listening on 9000, so there is no connection. (I am interested that ftp is listening, and wonder if that might not be a side effect of how it is rooted or an installed app.)

The test you need to do - and it was probably successful but not visible to you, from the success of the 3rd party app - is to issue commands using port 9000 FROM the NST itself.

The simplest way:

connect via ADB

su

from the ADB shell, try

telnet a.b.c.d 9000

where a.b.c.d is your squeeze / synology box.

If you get an answer, then you have reached it, and the problem is with teh Synology software.

I run a DS 409 at the house, and the Android client for the box, well, it is not very good.
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
Hi Guys,

I have a question about the update to version 4.1.2.

When I go to Settings > About > System update, I see that the update to 4.1.2 is found but it says that it is waiting to download but it stays like that forever and nothing happens.

Has anyone else seen such behavior? Do you know why it is happening and if it is normal?

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] b00mb00mchuck:
Maybe a stupid question but... are you connected to WiFi when you see the message?
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
Yes, of course I am :)

I also forgot to mention that I am fully stock, unrooted and locked.
[Nexus 7 Q&A, Help & Troubleshooting] mattrmay:
Make sure you have a good WiFi connection. The WiFi in my dorm shows a good connection (String signal) but the internet can sometimes timeout easily. Make sure your connection to the internet is superb.
[Nexus 7 Q&A, Help & Troubleshooting] Omar04:
Taking a quick look at your wifi icon its not transferring or receiving data. No black arows inside..
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
My connection is very good. For just in case, I put the Nexus besides the wifi router and still nothing happens.

Yes, I know what the arrows mean but my question is why this is happening? Is there a way for me to force the download? Or maybe I just have to wait more (it's been like this since yesterday)?
[Nexus 7 Q&A, Help & Troubleshooting] AnotherBill:
Try powering off the Nexus and then starting it up again. If that doesn't work, try using the technique to trick it into updating mentioned in this thread (yes, it's for a different situation but still worth a shot)

http://xdaforums.com/showthread.php?t=1930603
[Nexus 7 Q&A, Help & Troubleshooting] ondoy1943:
Take a look at this thread:

http://xdaforums.com/showthread.php?t=1934670
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
Hey, thanks for the suggestions. I tried powering off and on and it didn't work.

Then I tried the method to force stop the Google Services Framework and when I went to the System updates screen, I had the option to check for updates. I checked and I am back to where I was before - the update shows but is only "waiting to download" :(
[Nexus 7 Q&A, Help & Troubleshooting] krelvinaz:
Not really a solution but why are your locked?

Sent from my Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] porkus:
probably because he isnt in to rooting?? and just wants his update. not everyone on XDA unlocks and flashes im sure.
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
Well, I bought the N7 recently and I want to see how it feels without rooting and custom roms. But later on, I will most probably unlock it. :)
[Nexus 7 Q&A, Help & Troubleshooting] svetlio89:
Hi everyone. I have the same problem with the download. Mine N7 is also stock. Tried the method with the framework multiple times, tried to restart, tried another internet, still no luck in downloading. Any further suggestions?
[Nexus 7 Q&A, Help & Troubleshooting] spooooky:
Same issue here! I see the update, but it's waiting to download forever. Could this be connected to the location? Same as the the other guy I'm located in Sofia, Bulgaria.
[Nexus 7 Q&A, Help & Troubleshooting] wyvorn:
Yeah, I'm starting to think the same, as I am in Sofia too.

Anyway, I could not find a solution, so I rooted and installed CM10, so no issue for me anymore. :)
[Nexus 7 Q&A, Help & Troubleshooting] stangen:
Another one from Sofia. Waiting to download and after some time... unable to download.....
[TouchPad General] akarri:
My HP Touchpad on ICS (Cyangenmod 9) is refusing to start. Keeps flashing the message "Unfortunately Trebuchet stopped working" and when i touch on ok, the message pops up again.

this is the sequence in which it happened:

My daughter was playing Temple Run and the TP shut down because the battery was over.

I plugged it into the wall charger and after about 10 minutes of charging (the screen showed a big battery symbol with a red line beside it)

and then the boot screen came on, with cyanogen mod highlighted and in few seconds started to boot into ICS, and the screen showed - Cyanogen MOd 9 Loading - and stayed like that for 45 minutes;

I felt it got stuck and held the power button and vol up for a few seconds to reboot and this time it reboot with the Android icon with lots of blue around it. And thats when it started flashing the message "Unfortunately Trebuchet stopped working"

also the system tray (?) lower right corner, flashed a popup saying the sd card is damaged; and when touched it , showed the message 'sd card damaged - format or cancel- touch on either one and the Trebuchet message comes on...

went back to the boot screen and tried to boot into webOS, but somehow it jumped back into cyanogen mod.

i need help. do i need to reinstall the entire cyanogen mod package again and if yes, how do i do it?

and where is the sd card located? is it user accessible?

thanks
[TouchPad General] chicle_11:
The sd card is a virtual one, in other words, there is no sd card. It's created when installing android.

I recommend leaving the TP plugged into the charger for at least a few hours, then try booting again. If the problem persists, you might have to doctor. It's not hard. Go to the webos nation forum and search for webOS doctor and follow the instructions. It might not be a bad idea to uninstall android, then do a new, clean install. You should be good to go. BTW, try to not let the battery run down all the way. As you can see, it can cause all sorts of problems.

Good luck.
[TouchPad General] akarri:
thanks

Thanks; I have already cleared most of the problem by using webOS Doctor; I think I need to do a clean install, for that i have to uninstall cm9 by using the ACMEUninstaller, right? i am a noob, so...

will that help me recover some space, because now with just webOS on the HP Touchpad, I have just about 5 gigs?
[TouchPad General] sstar:
Yes use ACMEUninstaller to remove cm9 just do exactly what you did to install but replace ACMEInstaller2/3 with ACMEUninstaller.

For guidance my 32gig Tablet shows a hard drive size 27.2 with just webos and 25.5/25.4 with Android installed the lower figure using ACMEInstaller3 as it takes an extra 100mb .
[TouchPad General] chicle_11:
Read this thread : http://xdaforums.com/showthread.php?t=1426244 (read the whole thread).

This fixed my "lost space" problem. I had about 16gb missing, but this got the partitions 'right' Good luck.
[XPERIA X8 Original Android Development] Daveee10:
Jelly Bean Mini Project | Kernel 2.6.29.6

Info:

This kernel is part of JB Mini Project

Team Members:

Stelios97, Daveee10

Features:

Forked from nAa-ics-04 (all ICS features are already in there)

Built with linaro-4.7.1 toolchain

JBMini Recovery

Custom mtd partitioning scheme suitable for JB

Tracing support for JB

pmem: bring up2date with CAF 2.6.38

genlock/kgsl fixes

Triple buffering support for msm framebuffer

Much more RAM for improved multitasking experience (185MB)

Resized partitions (System:261MB, Data:191,8MB, Cache: 5MB, Recovery: 10MB)

Two version now: One with Single (JBMini Project) recovery and One with Dual (JBMini Project and TWRP) recovery

From v06 ready for use every JellyBean ROM like MiniCM

Install Instructions:

Unlock your bootloader

Download the kernel ftf file and move it to Flashtool\firmwares

Flash the kernel via Flashtool

(First time only) Get into recovery and format /system /cache and /data manually

For dual recovery version:

In this version the Aroma FileManager from JBMini Recovery doesn't work because I needed to delete that. With that the kernel image is now too big, so the kernel don't flashable... In the future this will be fixed with a little trick (The file manager included the rom) or only using the TWRP recovery if it's stable...

Enter to JBMini Recovery: press back button

Enter to TeamWin Recovery: tap the screen

Download:

DON'T mirror kernel​

v06: Goo.im | Dev-Host | Android File Host

v05a: Goo.im | Dev-Host | Android File Host

v05: Goo.im | Dev-Host | Android File Host

v04 dual recovery: Goo.im | Dev-Host | Android File Host

v04: Goo.im | Dev-Host | Android File Host

v03: Goo.im | Dev-Host | Android File Host

v02: Goo.im | Dev-Host | Android File Host

v01: Goo.im | Dev-Host | Android File Host

Sources:

The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.

https://github.com/JBMiniProject/semc-kernel-msm7x27-jb

Thanks:

NobodyAtall

Azuzu

Google

Stelios97

pilu1978 for porting TWRP for SEMC X8 (Original thread)

feherneoh

sgt. meow

And all who posting patches to gerrit

Please don't ask ETA!​

Press button or if you like and want to support this project!​
[XPERIA X8 Original Android Development] Daveee10:
Changelog:

2013.02.11 (v06)

-Added SmartassH3 CPU Governor

-DeadLine I/O Scheduler

-Change mounts for JB so now compatible with all Jelly Bean Rom

-Fixed SD-Card format issue

-Fixed JB Mini recovery backup issue

-Changed default I/O Scheduler to DeadLine

-Changed default CPU governor to SmartassH3

-Resized partitions similar to nAa-jb kernel (System: 261MB, Data: 191,8MB, Cache: 5MB, Recovery: 10MB)

2012.12.16 (v05a)

-Reduced RAM (185MB) because the OMX needed more ADSP memory for storing video

2012.12.16 (v05)

-Backport adsp_video_verify from 2.6.38 kernel

-FPS Uncapped

-Reduced RAM (186MB) because the OMX needed more ADSP memory

-Some more little change and fix

2012.11.14 (v04 Dual recovery) - Little changes but big step

-New kernel logo [thx to Stelios97]

-Dual recovery version

2012.10.20 (v04) - Some improvements

-Added SLQB memory allocator

-Lowmemorykiller small fix

-Patch for ScreenOff (Electron Beam) Animation

-RWSEM update to 2.6.35

-Futex backport from 2.6.32

-lib-CRC32 & crypto-CRC32 updates

-update jHash to V3

-New recovery (JBMini Recovery 1.0)

2012.09.08 (v03) - Add some features

-New CWM Recovery (JBMini CWM Recovery 6.0.1.1)

-Built in Aroma File Manager

-Triple buffering now working

-KGSL/genlock fix

-Some free memory (192MB) [thx to nAa]

-Resized partitions (System:260MB, Data:200MB, Cache:8MB)

2012.08.04 (v02) - Add some features

-Enabled vsync

-Enabled tripple buffering

-Lower gain value

2012.07.22 (v01) - First release
[XPERIA X8 Original Android Development] Daveee10:
Development: [in next release]

Latest TWRP recovery (2.4.1.0)
[XPERIA X8 Original Android Development] Daveee10:
reserved....
[XPERIA X8 Original Android Development] ithunter:
waiting for v4 ... :)
[XPERIA X8 Original Android Development] Neur0Nerd:
Try to do not ask for ETAs

Just let them some time because they are hard working, Kernel/Rom at the same time is a lot of time consuming.

Good luck to you guys ;)
[XPERIA X8 Original Android Development] ElmirBuljubasic:
Why another thread?
[XPERIA X8 Original Android Development] Daveee10:
Because this is a kernel another thread the rom... Why publish rom and kernel in one topic??
[XPERIA X8 Original Android Development] Arex780:
Why just don't You put Google logo in kernel in boot like in stock Nexus kernel? It will be really nice and... everyone know that You do this kernel...
[XPERIA X8 Original Android Development] TheSpaceManatee:
Lol hes waiting not asking when its going to be released
[XPERIA X8 Original Android Development] CnC-ROCK:
a noob Q....

this kernel has triple buffering...

does it have vsync or touch responsiveness too (any of the two other parts of project butter)?
[XPERIA X8 Original Android Development] iVolcaNoz:
sry but how to enter into the recovery mode?

i tried pressing all the buttons when the led is blinking but still failed..

thx..
[XPERIA X8 Original Android Development] Godra:
Changelog:

2012.09.08 (v03) - Add some features

-New CWM Recovery (JBMini CWM Recovery 6.0.1.1)

-Built in Aroma File Manager

-Triple buffering now working

-KGSL/genlock fix

-Some free memory (192MB) [thx to nAa]

-Resized partitions (System:260MB, Data:200MB, Cache:8MB)

2012.08.04 (v02) - Add some features

-Enabled vsync

-Enabled tripple buffering

-Lower gain value

2012.07.22 (v01) - First release
[XPERIA X8 Original Android Development] CnC-ROCK:
thanks for the highlight bro..

.i almost forgot to read initial features seeing that triple buffering was working...haa..

thanks again...

so since we have all 3 parts of project butter working.. that means that we have now project butter support from the kernel?

:fingers-crossed: nice work daveee10
[XPERIA X8 Original Android Development] Daveee10:
The rom using 60 FPS...
[XPERIA X8 Original Android Development] CnC-ROCK:
so project butter working right?
[XPERIA X8 Original Android Development] CnC-ROCK:
see change log

-Enabled vsync

-Enabled tripple buffering

and he said that rom runs on 60 fps ... so we have the project butter except the touch responsiveness part..... i am just confused.... just asking....
[XPERIA X8 Original Android Development] Daveee10:
Project Butter never working on this device...
[XPERIA X8 Original Android Development] MatthewWu:
Excuse me, does this kernel works with MiniCM 4.1.1 ?
[XPERIA X8 Original Android Development] Daveee10:
Yes it works if you format partitions after flash kernel...

I don't know what's working and what's not.. I think some things like Partition info not recognize SD-Card, but the useful things working...
[XPERIA X8 Original Android Development] Daveee10:
New version of kernel is released
[XPERIA X8 Original Android Development] Godra:
Thank you Dave :D

Is ROM going to be updated soon too?
[XPERIA X8 Original Android Development] Daveee10:
Very soon...

Soon I go to sleep and tomorrow i make some little changes what I'm forgot and update... Be patient... :)
[XPERIA X8 Original Android Development] MatthewWu:
Actually it can't work because the some reason.

It shows the name : "E15i", "E15a", E16i, E16a, shakira, shakira ( i don't know exactly)

Maybe it's the ROM / kernel problem, hehe..

Wait for the next release of your rom, ya! :D
[XPERIA X8 Original Android Development] vijayareddy4:
waiting for the new ROM

Kernel is fine. Waiting for the new ROM
[XPERIA X8 Original Android Development] ngoralph:
have you personally tried it??? becuase the past version were not compatible to minicm10 for me
[XPERIA X8 Original Android Development] Daveee10:
You must change MiniCM installer... Remove the validate script and change updater-script file for not run validate. The rom installing correctly...
[XPERIA X8 Original Android Development] sgt. meow:
@MatthewWu

I also got that error once. Restore a backup (I hope have one) of a JB ROM from the embedded CWM of this kernel. And then install the desired ROM from CWM again. It worked for me and I hope it works for you.
[XPERIA X8 Original Android Development] MatthewWu:
Thanks, Davee10 and sgt.meow. But, i ca't find any "validate" file (there's no validate file in miniCM 4.0.1) , and i find out a string that same with the error that shown on my phone. ( i found it at META-INF\com\google\android\updater-script)

i delete it (just try) and got "bad" error when install. What should i do? Or maybe it's better for me to just wait for your next release?
[XPERIA X8 Original Android Development] Daveee10:
If you want use our rom, wait for release the rom... If you want use MiniCM use nAa jb kernel...
[XPERIA X8 Original Android Development] danibosev:
Are kernel 04 working with Beta 2 ROM?
[XPERIA X8 Original Android Development] sgt. meow:
It should be.
[XPERIA X8 Original Android Development] ->Sid:
Is the rom's next release going to b still a beta...
[XPERIA X8 Original Android Development] ducthe134:
Are kernel 04 working with CM9 ROM
[XPERIA X8 Original Android Development] sgt. meow:
How would a JB kernel work with a ICS ROM? The answer is it won't.
[XPERIA X8 Original Android Development] ducthe134:
working for me
[XPERIA X8 Original Android Development] sgt. meow:
a JB kernel works on an ICS ROM? you sure?
[XPERIA X8 Original Android Development] fotis12:
I can't make a backup in recovery (stuck on backup android.secure), any solution?
[XPERIA X8 Original Android Development] chrissykess:
Still in it kenrel is bug, can;t create buckup?
[XPERIA X8 Original Android Development] CnC-ROCK:
this kernel is supports on JBmini Rom or other JB roms too?
[XPERIA X8 Original Android Development] Cancar96:
all roms have included tutorial in which you can see if your kernel has a match up.

for now i think that only this kernel is only for this rom.
[XPERIA X8 Original Android Development] FireMax_:
http://xdaforums.com/showthread.php?p=33374614
[XPERIA X8 Original Android Development] Daveee10:
New version released...

version 04 (Dual recovery)

Infos and link in first post
[XPERIA X8 Original Android Development] chrissykess:
Right now fixed make backup?

Wysłane z IXperia x8S dzięki Tapatalk 2
[XPERIA X8 Original Android Development] Daveee10:
Backup in JBMini Recovery freezing...

Backup in TWRP working only the android_secure backup don't work...

If TWRP got error when making backup mount manually the data partition in mounts menu...
[XPERIA X8 Original Android Development] Daveee10:
Dual recovery version reuploaded... Now it works perfectly
[XPERIA X8 Original Android Development] Daveee10:
v05 released with some changes... This version firstly for JBMP mini project jb rom Release 1 but usable with RC1
[XPERIA X8 Original Android Development] sgt. meow:
Hi Daveee10

You disabled HW vSync. I was wondering if SW vSync is also part of FPS-uncap too. It's easy to disable it. I was just asking. I think I'll try it today, if you give me the go. ;)
[XPERIA X8 Original Android Development] rounak:
what are the benefits of FPS uncaping ??? :confused:
[XPERIA X8 Original Android Development] sgt. meow:
Better performance in games, perhaps. No real improvement though.
[XPERIA X8 Original Android Development] pilu1978:
Basically you can get higher benchmark scores, but nothing more with FPS uncap. If a game can't draw more frames due the FPS limit, the game is smoother than enough, if the game can't reach the FPS limit and lags due the low FPS, it will NOT be faster without the FPS limit, so this option is good ONLY for benchmarks. :) (but removing the FPS limit has some disadvantages, sometime the scrolling lags, and the possibility of screen tearing is highly increasing)
[XPERIA X8 Original Android Development] sgt. meow:
Actually for some divine reason, users have reported that my kernel has somehow managed to increase gaming performance. I only disabled HW vSync. It doesn't result in screen cuts. None at all in 2 months. I think the SW bit causes the screen cuts, Will experiment with it.

BTW I saw this bit in the Xperia X10 forums. Hope it's the same for the X8. The file was pretty much where it should be. I'm just gonna change one 1 to 0 and see how that goes. And yeah FPS-uncapping does increase benchmark scores.
[XPERIA X8 Original Android Development] pilu1978:
I think (but not sure, this is only my own experience) the main reason of the screencut errors is somewhere in the clock syncronisations. When the AXI and AHB runs on same clock (or the one of these clocks is a multiplier of the other clock) I never had screencut errors (for example cpu runs on 768MHz with 192MHz AXI and AHB), if the bus clocks is different, the possibility of screencut errors is increased (for example the cpu runs on 691MHz, the AHB divided by 3 or 4 (I dont remember exactly) and the AXI is 160 (in nAa) or 192/200 (in alfs 8/9). My best settings in the cpuclock table is 384-576-768 (only these 3 frequency available) the AHB and AXI always run on 192. :) This settings give good balance between performance/battery (more clocks = more clock changes = more battery consumption). And the screencut errors also depends on governors (how change the clocks, and how many steps in clock changes).